1. Distributed Software Development
2011/12

2. Search4Yummy – Project Plan
Muhammad Sulyman, Jan Čustović
and Ronald Wolvers

3. Outline Deliverables Activities Plan Milestones
Development Methodology
Financial Plan
Communication
Project Risks
Questions

4. Deliverables Project Plan Requirement Engineering
Project Policies (SVN, Coding)
Project Design
Acceptance Test Plan
Test Report
Final Project Report
User & Installation Manual
Final Product

5. Activity Plan Activity W 41 W 42 W 43 W 44 W 45 W 46 W 47 W 48 W 49
Project Plan X
Requirement Engineering
Project Design
Implementation
Acceptance Test Plan
Alpha Prototype
Beta Prototype
Test Report
Final Product
User & Installation Manual
Final Report
Final Presentation
Plan
Buffer

6. Milestones 6. Final Delivery of Code and Documents 5. Beta Prototype
4. Alpha Prototype
3. Project Design
2. Requirement Engineering
1. Project Plan

7. Development Methodology
Waterfall model
Clear phases
Highly structured
Bad in practice
What if we want to change something in the previous phase?
Requirements
Design
Implementation
Verification
Maintenence

8. Agile software development
More flexible
Communicate, communicate, communicate 
Accelerated development
Key features:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

9. What are we going to use? Follow project plan
Individuals and interactions
Small team size and communication
Working software
Stick to deadlines!

10. Financial Plan 60€ / 1h (4h per work day)
Requirements gathering– 5days  1200€
Requirements analysis – 4days  960€
Design management – 24days  5760€
Implementation – 42days  10080€
Documentation – 10days  2400€
Testing – 10days  2400€
Total: 22800€

11. Financial distribution

12. Communication

13. Communication Bi-weekly meetings Central mailing list Skype/Gtalk
Progress
Problems
Supervisor attends
Central mailing list
Major issues
Skype/Gtalk
Minor issues

14. Project Risks Wrong choice of technology Lack of knowledge
Consider alternatives
Lack of knowledge
Discuss problems early
Skewed workload distribution
Carefully monitor hours spent
Too many requirements
Prioritize as much as possible

15. Questions?