"
Team:Groningen/Project Plan/Construction
From 2009.igem.org
Revision as of 12:31, 23 June 2009 by JolandaWitteveen (Talk | contribs)
[http://2009.igem.org/Team:Groningen http://2009.igem.org/wiki/images/f/f1/Igemhomelogo.png]
|
|---|
| Risk List | Tools and Documentation | Inception | Elaboration | Construction | Transition | |||||||||||||||||
| 1 | 2 | 1 | 2 | 1 | 2 | 3 | 1 | 2 | ||||||||||||||
| apr. 20 | may 18 | jun. 01 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | okt. 15 | ||||||||||
This is the iteration plan for the Construction iteration(s). See [http://www.upedu.org/upedu/process/artifact/ar_itpln.htm the UPEDU artifact description] for information on what this is and what it contains (including a template).
Milestone
These are the major [http://www.upedu.org/upedu/process/itrwkfls/ms_ioc.htm milestone objectives] for the Construction phase:
- TODO Our wonderful buoyant, metal filtering bacteria should be alive and kicking!
- TODO (?) The lab/plan cloning strategy should be fully worked out at the end of the phase to reflect our final decisions on which parts/protocols/procedures/? to use. (I think this roughly corresponds to the Implementation Model in UPEDU. --Jaspervdg 11:09, 23 June 2009 (UTC))
- TODO The Iteration plan for the transition phase completed and reviewed.
- TODO (?) Design Model (and all constituent artifacts) updated with new design elements identified during the completion of all requirements. (I think this can roughly be seen as fleshing out all the device designs and parts, or in other words: making sure The Project is up-to-date. --Jaspervdg 11:09, 23 June 2009 (UTC))
- TODO More?
Resources
- Note that we're opting to do this for the entire phase instead of each iteration as in UPEDU as this seems more natural (our needs change little over the course of one phase). --Jaspervdg 11:01, 23 June 2009 (UTC)
[Resources needed for the phase — material, human, financial, and so on.]
Construction 1
Plan
End date: 2009-07-21
Overall objective:
- The basic model should be ready
- The seperate part of the labwork should be known and working or almost working
- modellers should know which parameters they need so the labworkers can prepare providing these
- The tickets and hostel should be booked
Tasks per role:
- Analyst
- Change Control Manager
- Role not used (yet).
- Configuration Manager
- Designer
- Facility Manager
- Implementer
- Have genes as BioBricks in the vector, together with all DNA elements needed for expression (RBS, term etc).
- Work on the final parts should have been started.
- Try to find protocols for the characterization, to check feasibility.
- Keep record of the labwork on the Notebook site
- Integrator
- Modeller
- Project Manager
- Have both modellers and labworkers up and running.
- Labworkers have choosen the parts and tested those. The bouyancy, metal intake and accumulation should be tested and working seperatly.
- Have a start-up model and make sure the labworkers know which parameters the modellers need and can or already have provided these.
- Have choosen a tester, a "testplan" should have been made, the necessary equipment should be at least ordered.
- the tickets and hostel should be booked, so plans for jamboree or thereafter should be known roughly.
- Public Relations Officer
- Reviewer
- Scribe
- Stakeholder
- Tester
- Treasurer
Use Cases
[List the use cases and scenarios that are being developed for this iteration.]
Evaluation Criteria
[Functionality, performance, capacity, quality measures, quality goals, and so forth.]
Construction 2
Plan
End date: yyyy-mm-dd
Overall objective:
Tasks per role:
- Analyst
- Change Control Manager
- Role not used (yet).
- Configuration Manager
- Designer
- Facility Manager
- Implementer
- Integrator
- Modeller
- Project Manager
- Public Relations Officer
- Reviewer
- Scribe
- Stakeholder
- Tester
- Treasurer
Use Cases
[List the use cases and scenarios that are being developed for this iteration.]
Evaluation Criteria
[Functionality, performance, capacity, quality measures, quality goals, and so forth.]
Construction 3
Plan
End date: yyyy-mm-dd
Overall objective:
Tasks per role:
- Analyst
- Change Control Manager
- Role not used (yet).
- Configuration Manager
- Designer
- Facility Manager
- Implementer
- Integrator
- Modeller
- Project Manager
- Public Relations Officer
- Reviewer
- Scribe
- Stakeholder
- Tester
- Treasurer
Use Cases
[List the use cases and scenarios that are being developed for this iteration.]
