How to Use the Current Task List(Ref Id: 1277757466) If you scan down the Current Task List the most current working item is the first one that does not contain '(complete') at the beginning. At the time of this writing this project is at the 'Preliminary effort and schedule targets created and reviewed' segment before the 'Project launch/feasibility study complete' milestone.
Yes, this means the project is not in the coding phase. I gave my original reviewers plenty of time to read and understand the Project Vision and Business Case (see Docs section of this site) before moving on. This was a necessary precursor to the eventual 'go and no go' decision that will be made at step 31, the 'Planning Checkpoint Review' where a more formal go/no go decision will be made.
The Current task list consists of every milestone in the project (see the items in bold that start with the keyword 'Milestone'). The milestones indicate at what percentage the project can be considered complete. For instance, the project is somewhere between 10-20 percent complete when the software architecture is documented (that is, the milestone has been reached) after the previous, or lower numbered, items have been finished like the 'Staged Delivery Plan' and 'Software test cases for Stage 1 created' items.
One Business Case reviewer commented that perhaps the best approach for the project would be to just start writing code. This is exactly the opposite of how this type of project should be run for several reasons, including:
- One of the major goals of this project is to provide freely available documentation and transparency. This should include design documentation and discussions about planned functionality.
- Writing code without some kind of planning (use cases, agile stories, class-responsibility-collaboration cards, coding standards, etc.) is likely the mistake many open source LIMS initiatives suffered from in the past. Prospective users will perform a review of the design and development methodology used by the product authors and, when they find it missing or ad-hoc as in the case of many open source products, will be more likely to reject it.
- In the case of this project, the source code is the product, so a some familiarity with the decision-making methodology and development constraints will become necessary at some point. It makes sense to introduce it early and reiterate it often.
At this point the project is still in 'pre-work' and there are twenty three items in this segment. Many of these items involve documentation so as these items are complete the document section of the LIMSExpert.com site will grow accordingly. Go Back
Citation: How to Use the Current Task List. (2010). Retrieved Sun Apr 30 05:03:17 2017, from http://www.limsexpert.com/cgi-bin/bixchange/bixchange.cgi?pom=limsexpert3;iid=readMore;go=1277757466