Question

Explain the difference between how Agile handles the constraints and how Traditional/Waterfall handles the Constraints.

Would you ever create a WBS on an Agile project? Explain your answer.

Explain the distinction between the Essential System and the Envisioned System.

Which of the Agile Principles can successfully be applied to Waterfall/Traditional Project Management? Explain.

Answer 1

Agile and waterfall are the two methods which are used in project management.

The waterfall which stands for the traditional approach to project management in this method all the information on the work process is set in advance i.e a plan is set which is systematic in approach and all the work has to be dealt with a plan. This type of approach can be said as a linear approach to developing the software where a certain milestone change can be allowed if the customer wants any changes. Customers and makers of software work before the start of the project so that they could sort out the feature they need in the software, application. all goal is predetermined in advanced before the start of development. so waterfall handles constraints not so easily as this work process is not much flexible i.e some contract term has to be there. so there is not much scope of handing constraints as all work is predefined to do it the previous process has to be changed in which constraint depends.

In agile system development, all work is divided into a sprint with certain time frames these sprints all defined in advance which has a task associated that has to completed according to their time frames which are defined at the start of making a sprint. so there is a time frame for the deliverable. These deliverables are determined by customers according to needs and priorities and if there is a change in some features sprint has to be redefined and work is done accordingly so there is flexibility in the process. The constraint if developed is can be handled easily as there are sprints that can be altered but there is a cost involved in the process.

Creating a WBS  on an agile project can be done in various sprints. the work in a sprint can be divided into a number of small components and there should be a time frame to do it. hence the whole project is divided into sprint and sprint is further decided into some waterfall components known as work breakdown structure

An essential system is the minimum set of requirements that the customer wants in their required product has to be defined. so that all essential requirement is meant. Whereas in the envisioned system all the requirements which the customer needs in their product all set of features that have to be there when ordering is done are to be defined.

To apply the agile principle in the waterfall/ traditional approach one can use the agile component i.e sprint techno planning, requirements in some process like documenting, gathering information, budgeting this process has to be time-boxed like in the agile system. other processes like testing and Maintainance can also be done by the agile technique in waterfall system.