3. The benefits of iterative development on a project are:

It encourages user feedback.

The system grows by adding new functions to each development iteration.

Misconceptions are identified upfront.

Continuous testing is performed throughout the project.

Allows for lessons learned on previous iterations.

4. The benefits of adopting a project methodology include: (1) it adds value to the business in terms of repeatable standard, (2) it provides a uniform way for projects to be managed, and (3) it provides a platform to introduce quality and planning into the project.

5. An organizational structure has a direct effect on the manner in which projects are staffed, equipped, and managed through the chosen life cycle. Large organizations with many departments working in a matrix or functional structure may take longer to complete than a project structure with everyone assigned by project rather than by department.

6. Most projects today fail because of:

Poor communication. Poor estimation. Improper deployment. Ineffective user requirements. Poor change control.

7. Yes, a project methodology adds value to projects where no methodology is present. A methodology is not a silver bullet that excuses poor planning and deployment; instead, it guides the team on proper techniques and checklists, which will negate many of the obstacles found on projects today.

8. The waterfall methodology is the most common methodology found today. It is linear in approach most tasks are sequentially aligned to the previous and next tasks. The spiral methodology iterates the processes of planning, designing, building, testing, and delivering, until the system is ready to be released to the client.

References

Adaptive Development Methodology, SCRUM© 06/28/2002. Cockburn, Alistair. Human and Technology Manifesto. p. 1, 2000.

Fowler, Martin. The New Methodology, Thought Works, 2001. Available at www.martinfowler.com/articles.

Hamel, Gary. Leading the Revolution, HBS Press, 2000. p. 56.

Martin, Robert. Available from www.objectmentor.com/publications/RUPvsXP.pdf.

Michaelson, G. Sun Tzu, The Art of War for Managers, 2001. pp. 7, 14.

Musashi, M. (T. Cleary, Translator). The Book of Five Rings. Boston: Shambhala Publications, 2000. Strengthening the Case for Pair Programming, IEEE Software. July/August 2000.

Team LiB II I * previous next *