Agile Project Management Set 2

Must have a good understanding of Agile techniques ✘ Will always receive worse systems than their non-Agile counterparts ✘ Will typically get business value delivered early ✘ Will need to work out at the gym regularly ✔

Everyone must stand for the whole time ✘ The meeting must be short and well structured ✘ The Project Manager must ensure it is clear to all which team members are not performing ✘ No-one is allowed to leave the stand-up meeting until all problems raised have been solved ✔

Sponsor and Executive Management only ✘ Project Manager and Technical Leads only ✘ Project Leader and Customer Representatives only ✘ The entire team ✔

Storming ✘ Warming ✘ Calming ✘ Yawning ✔

The team can work all night, every night if enough pizza is provided ✘ The team should be expected to work overtime towards the end of the project ✘ The team should strive for a sustainable pace and a normal working week ✘ The team will "burn out" if they have to work overtime for more than two timeboxes (iterations) in a row ✔

All project stakeholders should attend every requirements workshop ✘ Retrospectives are only run at the end of a project ✘ It is best if project manager facilitates the project ✘ A facilitator will manage the structure of a facilitated workshop ✔

Get something quick and dirty thrown together to save time ✘ Get something simple up and working as quickly as possible ✘ Get something business-valuable delivered as quickly as possible, consistent with the right level of quality ✘ Get something delivered once it has been fully documented and the documentation signed off as complete and unchangeable ✔

The team should allow only senior managers to sign off deliverables ✘ The team should get acceptance of project deliverables from the appropriate stakeholders at least at the end of every timebox / iteration ✘ The team should get acceptance of project deliverables from the users during a UAT phase at the end of the project ✘ Acceptance of any particular deliverable on the project is gained from all stakeholders at the same time. ✔

The products produced by an Agile project should be cheaper than those produced by any other approach, but quality will suffer ✘ The products will be more expensive than by any other approach but will be top quality ✘ The products will be fit for purpose, but may not do what the customer wanted ✘ The products will be of appropriate quality, as guided by the customer representative involved throughout the development process ✔

A big design up front is always a good idea ✘ Just enough design up front gives a good foundation to start from and helps to mitigate risk, without unnecessarily wasting time ✘ No design up front is the best approach as most of the fun of a project is discovery of the unexpected ✘ Design has no place in an Agile project ✔