1. VirtuCo :: Process description ::

2. :: Reference ::

3. xyzxyzy Iterations

4. Iteration x Activity 1 Activity 2 Activity 3 Activity 4 Activity 5 Activity 6 duration ITERATION Reference

5. Activity x 1.Tasks that make up the 2.activity Input artefacts Artifacts (documents, or something else tangible) used as input to an activity Agents (roles) Main contributors to this activity ACTIVITY Reference Input artefacts Artifacts (documents, or something else tangible) used as output from an activity Techniques / tools Tools / techiniques that help doing the tasks

6. :: Process description ::

7. Project planningImplementation 1Implementation 2Implementation 3Delivery

8. Project planning 1.Write plan 2.Write requirements 3.Identify risks 4.Document tech. consider. 5.Create progress report Input artefacts Customer requirements Course demands Output artefacts Project plan Req. docucment Risk mgmt document Technical considerations Progress report Agents (roles) Project manager Architecture supervisor

9. Implementation 1 Cycle planning Design Implementation Testing Iteration delivery Next Iteration planning 4 weeks

10. Cycle planning 1.Identify use cases to implement in this cycle 2.Update requirements 3.Write acceptance tests Input artefacts Test/Bug reports Customer feedback Project plan Req. document Output artefacts Updated project plan Updated req. document Acceptance test cases Agents (roles) Project manager Test manager

11. Design 1.Update system architecture 2.Start design work Input artefacts Project plan Req. docs Customer feedback (Technical doc.) Output artefacts Updated technical doc. Agents (roles) Architecture supervisor Senior programmer Client / Server team leader Techniques / tools Design patterns Refactoring

12. Implementation 1.Continue design. 2.Write unit tests first! 3.Spikes, if uncertain what to do 4.Correct bugs 5.Code 6.Write integration tests 7.Update technical doc. Input artefacts Project plan Req. document Technical doc. Bug reports Output artefacts Incremented software? Automated unit tests Automated integr. tests Updated technical doc. Agents (roles) Senior Programmer Programmer Test manager Techniques / tools Design patternsJava coding conv. AntJUnit SCM guideBugzilla Refactoring

13. Testing 1.Acceptance test 2.Usability test 3.Report bugs 4.Report test results Input artefacts Acceptance test cases Software Output artefacts Test report Bug reports (in Bugzilla) Tested software Agents (roles) Test manager Configuration manager Usability specialist Tester Techniques / tools AntBugzilla

14. Implementation 1 delivery 1.Create progress report 2.Prepare delivery package for course 3.Prepare delivery package for customer Input artefacts Updated project plan Updated req. document Technical spec. Test cases (document) Test report Test log Tested software Output artefacts For course: documents + progress report For customer: Course pkg + tested software Agents (roles) Project manager Document manager Configuration manager

15. Next iteration planning 1.Decide with customer what usecases will be implemented in next iter. 2.Enter tasks in Trapoli Input artefacts Customer feedback Project plan Req. document Output artefacts Updated project plan Updated req. document Agents (roles) Project manager Customer Techniques / tools Trapoli