Chapter 2. J2EE Software Development Methodologies

In This Chapter

(Not) Gaining a Competitive Edge in Internet Time
Why J2EE Projects Fail
The Top Ten Checklist for Initiating J2EE Projects
Organizational Frameworks for Supporting Enterprise J2EE Projects
Software Development Methodologies
J2EE Software Development Methodologies Unveiled

As stated by The Standish Group, a leader in gathering metrics on the IT industry

Approximately 40% of all IT software development projects are destined to be cancelled before their completion dates.
Approximately 30% will be heavily challenged by cost and time overruns, or changes in project scope.
Approximately $145 billion will be spent on cancelled or challenged projects.

The objective of software development projects is not to fail or become so challenged that failure is the only option. However, if they possess the "four C's" of project management, Complexity , Causes , Confusion , and Costs (James H. Johnson, chairman of The Standish Group), you can have a high confidence level that there will be problems.

At the root of all J2EE software development projects are two attributes that need to be effectively managed to promote success:

The Humanistic attribute ” People, each with their own personalities and skills, play a vital role in sponsoring, managing, and conducting the activities within a project.
The Methodology attribute ” A disciplined process is necessary to ensure that the J2EE software development effort is planned and executed in the most optimal manner, hence providing controlled and predictable results.

This chapter's objective is to provide you with a unique perspective on why J2EE projects either succeed or fail, through the application of software methodologies. An exhaustively detailed study of the current methodologies applied to deliver J2EE solutions is beyond the scope of this book. However, you will learn the origins and existing implementations of current methodologies, as well as a balanced view of the issues or concerns you will have to address by using them. Once you have armed yourself with this knowledge, you will be able to decide the most appropriate methodology that adapts to your J2EE project.