Agile Project Management

May have ✘ Major ✘ Must Have ✘ Mandatory ✔

Has no control over the prioritization of delivered features ✘ Has total control over the prioritization of features ✘ Collaborates with the developers over prioritization of features, but the developers have the final decision ✘ Collaborates with the developers over prioritization of features, but the business has the final decision ✔

Do no documentation ✘ Do plenty of documentation, to prove you have done a good job ✘ Do the necessary documentation to support the use of the product ✘ Do more documentation than usual, because Agile is risky ✔

To produce working product early and incrementally ✘ To produce working product after documentation has been signed off ✘ To produce simple prototypes early, but no finished product until the end of the project ✘ To produce products without any technical integrity ✔

No design up front ✘ Big design up front ✘ Just enough design up front ✘ Use a previous design ✔

The Agile leader might lose their job as the team is doing all the work ✘ If the team fails, the Agile leader will not get a performance bonus ✘ ect control over the team ✘ The Agile leader cannot share the glory of team success ✔

A list of activities that can be banned by the team ✘ The set of Won ✘ A visible chart of work for the team ✘ A ban on fizzy drinks within the team ✔

Teams work less well when it rains ✘ Keeping metrics of earlier work to help with future estimates ✘ Retrospectives should include less important topics such as the weather ✘ Estimating is as futile as predicting the weather ✔

It is more fun for the developers ✘ Many projects are evolutionary, and a better solution emerges this way ✘ It is boring to try to analyse everything at the beginning of a project ✘ It gives a good reason for late delivery ✔

Is self-organizing, so needs no specific skills ✘ Collaborates and supports team members ✘ Ensures that weak members of the team are thrown out of the team ✘ Ensures blame is allocated fairly ✔