Learn about common pitfalls associated with agile retrofitting.
- I once worked for an organization … that had a long history of traditional project management. … They maintained a template library for every report. … It represented decades of work. … It was a gift from previous project managers. … The charter template was so old … that it included an explanation of email. … I remember it said, this charter can be redistributed … using the newer electronic message format. … It was a great resource. … A new project manager could plug in the templates … and immediately get to work. … Everybody knew what to use, … and everybody knew what to expect. … But this library ended up being an obstacle for the team. … For traditional project managers, … these resources are tough to abandon. … What often happens is an organization … will try to retrofit the documents to make them more agile. … It's important to avoid retrofitting your documents … to make them more agile. … Instead, create new documents. … If you can, use existing agile charts and reports. … Making this decision itself can be a process. …
- Explain the purpose of a taskboard and how it can help keep a project on track.
- List the correct order of the swim lanes on a taskboard.
- Name the two types of burndown charts.
- Recognize the problems that occur when a team does not break down epics into stories.