Then, I created the rubric scoring criteria using this tutorial: It worked great, but now I can't figure out how to tie the score back to the project table (in the tutorial, he did it all in one table), or at least tie each ProjectID to a single Score. I created a bare bones ProjectTable with primary key ProjectID. Phase is a big deal at work, because different folks are in charge at different phases and people are always pointing fingers about tasks not being complete prior to moving to the next phase. I could have separate table for project details, milestones or "to-do" items, but not sure how I would show which phase each project is in. But if I do it that way, all the relationships would be one-to-one.So wouldn't it be better to just make everything in one giant project table like we already have? If not, I'm not sure how to approach. My first instinct was to setup a table for each phase. I am having trouble figuring out how to setup the database. The columns are currently a mashup of project details (title, POC, cost, etc.), milestones/status (received funding, awaiting contractor, awaiting test), and "to-do" list items (request funding, create drawings, write reports, build prototype). Up to this point, the details have been kept haphazardly in one giant excel spreadsheet with a bazillion columns. It worked great, but the boss wants it connected to all the project details which are kept separately. So I made a little scoring rubric in Excel that asked some questions (size, cost, ROI, etc.) and made a standard score based on the answers and spit out the score and title of the project to a table so you could sort by highest priority. So our biggest problem tended to be consistently prioritizing. We always have more work than we can feasibly accomplish with time/budget. Every project we do follows the same basic process with distinct phases: Identify Issue, Research, Design, Build, Test, Field. I'm trying to build a project tracker database for work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |