Agile and Water Project Management

How to Manage Project Scope?

* Monitoring the project's status and baseline scope * Comparing actual work performance measurements with the baseline scope using variance analysis: "How different is the current project from the original plan?" * Determining the cause and the degree of the changes found * Deciding on change requests, i.e. whether corrective or preventive action is needed * Managing all change requests and recommended actions (whether corrective or preventive actions) via the Perform Integrated Change Control process * If approved change requests affect the project's overall scope and cost baseline, then the scope statement, Work Breakdown Structure (WBS), and/or cost baseline is updated and sent out to stakeholders In short, all changes are processed, documented, and communicated properly.

What are the eight stages in Waterfall Project Management?

1 Conception, 2 Initiation, 3 Analysis, 4 Design, 5 Construction, 6 Testing, 7 Implementation, and 8 Maintenance

What are the four principles which are typically used to highlight the difference between agile and waterfall (or more traditional) approaches to project management?

1. Customer collaboration over contract negotiation 2. Individuals and interaction over process and tools 3. Responding to change over following a structured plan 4. Prototyping/working solutions over comprehensive documentation

What are five advantages of the Agile Methodology?

1. It allows for changes to be made after the initial planning. 2. It's easier to add features that will keep you up to date with the latest developments in your industry. 3. At the end of each sprint, project priorities are evaluated. 4. The testing at the end of each sprint ensures that the bugs are caught and taken care of in the development cycle. They won't be found at the end. 5. Because the products are tested so thoroughly with Agile, the product could be launched at the end of any cycle.

What are five Disadvantages of the Waterfall Methodology?

1. Once a step has been completed, developers can't go back to a previous stage and make changes. 2. Rlies heavily on initial requirements. 3. If a requirement error is found, or a change needs to be made, the project has to start from the beginning with all new code. 4. The whole product is only tested at the end. 5. The plan doesn't take into account a client's evolving needs.

What are three advantages of the Waterfall Methodology?

1. Stresses meticulous record keeping. Having such records allows for the ability to improve upon the existing program in the future. 2. The client knows what to expect. They'll have an idea of the size, cost, and timeline for the project. 3. In the case of employee turnover, waterfall's strong documentation allows for minimal project impact.

When you should use waterfall methodology?

1. When there is a clear picture of what the final product should be. 2. When clients won't have the ability to change the scope of the project once it has begun. 3. When definition, not speed, is key to success.

What are two disadvantages of the Agile Methodology?

1. With a less successful project manager, the project can become a series of code sprints. If this happens, the project is likely to come in late and over budget. 2. As the initial project doesn't have a definitive plan, the final product can be grossly different than what was initially intended.

Which methodology do you use if the project is going to be changing rapidly?

Agile

What approach does agile traditional treat to do?

Agile commits set resources over limited periods to deliver products that are developed over successive cycles.

What is the Individuals and interaction over process and tools principles differences between agile and waterfall?

Agile emphasizes a shift from a control to consensus. Focus is on people achieving benefits through engaged, accountable, high performing teams with focus on sharing data, openness, team communication and learning from feedback. A behavior change in management roles of the team become both serving and leading to create commitment and accountability to an end goal.

What are the principles of agile working? (Similar to what is Agile Project Management?)

Agile helps respond to changing requirements. It focuses on delivering maximum value against business priorities in the time and budget allowed, especially when the drive to deliver is greater than the risk.

What is Agile Project Management?

Agile uses short development cycles called "sprints" to focus on continuous improvement, scope flexibility, team input, and delivering essential quality product or service.

What led to the creation of agile methodology created?

Disadvantages of the waterfall methodology. Instead of a sequential design process, the agile methodology follows an incremental approach.

What is the Customer collaboration over contract negotiation principles difference between agile and waterfall?

How a project is delivered is driven by a team working with end users, focus is on a core deliverable and iterating over time. Agile favours benefits and innovation through collaboration with a particular focus on customer satisfaction, quality, teamwork and effective management.

Osmotica

Immucor Seneca Acella

When does Scope creep occur?

It can occur when the scope of a project is not properly defined, documented, or controlled. However Scope creep is typically caused by key project stakeholders changing requirements, or sometimes from internal miscommunication and disagreements.

What is Waterfall Project Management?

Much like construction and manufacturing workflows, waterfall methodology is a sequential design process. Each of stages are completed before developers move on to the next step.

Which methodology do you use when you know exactly what you need?

Waterfall

What is Scope creep (also called requirement creep, or kitchen sink syndrome)?

Refers to how a project's requirements tend to increase over a project lifecycle, e.g. what once started out as a single deliverable becomes five. Or a product that began with three essential features, now must have ten. Or midway through a project, the needs of customers change, prompting a reassessment of the project requirements. In other words Scope creep is Adding additional features or functions of a new product, requirements, or work that is not authorized (i.e., beyond the agreed-upon scope).

What is the Prototyping/working solutions over comprehensive documentation principles difference between agile and waterfall?

The team owns the MVP working together to develop the product; what they will deliver and how they will deliver it. The delivery team is 'cocooned' to focus on the solution to the problem they are dealing with. The team will make constant adjustments to the scope of the product.

What is the Responding to change over following a structured plan principles difference between agile and waterfall?

Waterfall uses an agreed scope to create a time and resources plan. Agile establishes the resources and time which ultimately drive scope. There will be a number of time and cost delivery windows, sprints, through which the project will evolve. An agile environment establishes a minimum viable product (MVP); the core project deliverable to trigger the start of a delivery. This is likely to change as the project team realities other opportunities or benefits that become available throughout each sprint.

What approach does waterfall traditional treat to do?

Waterfall will tend to treat scope as the driver and calculate the consequential time and cost. Waterfall will tend to treat scope creep as a deliverable and calculate the consequential time, cost, labor, and material. Waterfall will tend to implement changes quietly and less time consuming.

What is Scope?

What a project will produce (product scope) and the work needed to produce it (project scope).

Which approaches to project management is best to use?

You should use a 'golf-bag' approach to selecting the right techniques that best suit the project, the project environment and the contracting parties with an emphasis on the behaviours, leadership and governance, rather than methods, that create the best opportunities for successful project delivery.