Join Doug Rose for an in-depth discussion in this video Communicating progress, part of Agile at Work: Reporting with Agile Charts and Boards.
- Traditional projects are like a submarine.…Most of the work happens below the water line.…And every so often, the project surfaces…and sends a signal to the rest of the world.…These signals usually come in the form of…executive summaries and high level status reports.…These reports took a long time to create.…They're also not needed by the team.…The team was hard at work within the submarine.…They don't need to be updated on their own progress.…When I was a traditional project manager,…I would create two sets of reports.…
One for the team, and one for the stakeholders.…I would work on each set independently.…I updated the internal reports daily.…Then it would translate the same information…into an executive overview.…I spent a good deal of my time communicating…the team's progress in both directions.…I would ask questions for the team,…then I would report answers to waiting executives.…In Agile, the team focuses on working software.…There's much less emphasis on creating documentation.…
This is a key value in the Agile Manifesto.…
Bonus: Watch the bonus chapter at the end of this course where Doug answers common questions about the agile mindset, including what types of projects would be the best fit.
Lynda.com is a PMI Registered Education Provider. This course qualifies for professional development units (PDUs). To view the activity and PDU details for this course, click here.
The PMI Registered Education Provider logo is a registered mark of the Project Management Institute, Inc.
- Communicating progress
- Prioritizing the backlog
- Showing daily progress with a taskboard
- Sizing taskboards
- Creating a burndown chart