Summary

Just as wireless devices/PDAs today have slowly started to replace connected desktop/laptop systems, we see newer, agile, lightweight methodologies advancing as possible replacements for the more rigid heavyweight methodologies. From the methodologies discussed in this chapter, we see that there are numerous methodologies across all industries light, heavy, and hybrids. They differ in the number of people involved in the project, the criticality of the project, the project priorities, and, probably, by the personal philosophies of the people involved in these projects. If you didnt find the ideal methodology in this chapter, simply use the best one of all the mentioned methodologies and expand on it. Supplement it with templates and assess the processes needed most. A good development methodology optimizes quality, consistency, and timeliness of delivery.

Whether you use PRINCE2, RUP, RAD, Waterfall, Open Source, Scrum, Spiral, or another, you should be familiar with these underlying concepts. One project may require one approach while another project may need something unique. While projects differ in size and complexity, your unique project approach is based on using key building blocks to understand what needs to be done when designing/using a methodology. These building blocks are:

Understanding and assessment of the engagement and the solution to be implemented. Before initiating an engagement, the project team works to understand the intricacies of the problem. From this flows a comprehensive assessment of the solution to be developed, including time lines and budgets.

Planning the full scope of the project. Based on the assessment, a detailed project plan is assembled. This includes schedules, milestones, staffing, risks, and dependencies. Over the life cycle, the project plan becomes the foundation and framework for all activities.

Team design that assembles the best group of professionals for the job. Project teams are assembled not only based on the technical acumen required, but also on domain expertise in solving specific business problems.

Project management that ensures a timely delivery within your budget. The team relies on a combination of industry best practices and techniques to ensure that projects come in on time and within budget.

Communicate to project teams that any project methodology should follow a structured, yet flexible approach, be able to deliver quality, and ensure client involvement at all times.

Lessons Learned

The following lessons are crucial in understanding development methodologies:

Simply adopting a methodology is not feasible without a thorough assessment and gap analysis.

Dont try to sell a Rolls Royce to an organization that requires only a Jeep. Sometimes they really dont need all the flash.

Gaining executive support for moving ahead with a methodology is paramount to the success of any organization. Without executive support, it becomes increasingly complex and time consuming.

Determine your business strategy first, and then focus on the tactics you wish to employ.

Ц±кШ=1 иллл1М1Ы1[

Questions

1. When dealing with a waterfall methodology, can one proceed with the life cycle if the requirements have not been finalized and signed off on by all parties?

2. Define heavy and light methodologies.

3. Name the benefits of iterative development on a project.

4. Explain how you would convince your client or organization of the benefits of adopting a project methodology.

5. Does the type of organizational structure affect the efficiency by which proj ects are managed?

6. List five reasons that most proj ects fail today.

7. Based on your answers in the previous question, would a proj ect methodology resolve these failures?

8. Describe the difference between the spiral and waterfall methodologies.

Answers

1. No, a waterfall methodology requires or emphasizes that one phase needs to be completed before the next phase begins. If the user requirements are incomplete, the subsequent phases become extremely complex, which is likely to result in schedule and cost overruns.

2. Heavy methodologies are predictive in nature, which results in many unsuccessful projects. A heavy

methodology takes time; the design and deployment are dependent on each other. Light methodologies are more agile and adaptive in nature. They focus on being more informal, yet communicative. Light methodologies are designed and built face-to-face so that information flows more freely and swiftly than a heavy methodology would.