System Analysis and Design - Agile Software Developement The Agile movement star

Question

System Analysis and Design - Agile Software Developement

The Agile movement started partly in response to a high failure rate of complex software projects in the later part of the 20th century and continuing on into the present. This phenomenon has been referred to as the Software Crisis. One of the factors that can contribute to the failure of a software project to complete on time and/or on budget is changing requirements. For large projects it is possible for the project to take so long to complete, that the business rules change due to changes in the environment the business is operating in (government regulation, tax laws, new competition, etc.).
Agile Development has several values. One of which is responding to change over following a plan. In addition one of the first principles of Agile Modeling is developing the software is your primary goal. Taken to an extreme (and there is an Agile Methodology called eXtreme Programming, aka XP), this can lead to a team valuing the development of quality software and responding to changes to the exclusion of other activities that do not generate working code for the customer (e.g. Keeping a detailed and up to date plan, status meetings with management).

1. Do you think it is possible that a team that was strictly following Agile Development values and principles would have a conflict with the expectations of a traditional manager used to a high ceremony project (lots of reports and documentation).

2. If you think there would be a conflict tell us what is it and why it arises. If you don’t think there would be a conflict, tell us why it would not occur.

Explanation / Answer

It is definitely possible that conflicts may arise between an agile development team and a traditional manager. In traditional practices like Waterfall model a sharp emphasis is given on proper documentaion of requirements and on reporting project progress. In some cases this documentation required more time than the development of software solution. One can not definitely ignore the merits to document everything.But when documentation start appearing as an obstacle to deliever the best in the most efficient time then one needs to rethink the strategy for project management. Comprehensive planning is done in traditional model to reduce risks and deliever an efficient solution in estimated time to the client. Such practices make sure that onshore and offshore team are in sync over requirements and there is least possibility of conflicts between client and developers understanding. A traditional manager can not overlook these factors even in an agile model so easily and hence chances of conflicts( on how time should be allocated for each phase and how duties are distributed for individual role) may arise. The shift from a traditional practice to agile one needs a good understanding between client, management and developers.  

Related Questions

Navigate

• Browse (All)
• Browse S
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.