What's an accidental agile project manager, you ask? Anyone who suddenly and unexpectedly finds themselves responsible for an agile project. Maybe the home remodel project turned out to be a little more difficult and complex than you expected. An organization you volunteer for may need a project to build a new wing for an orphanage and asks you to help. Or your manager gave you a project management book and put you in charge of an important work project. In business, it's not uncommon to see team leaders doing project managers' work, and they may not even be aware.Congratulations, you just became an accidental agile project manager!This book is the missing agile project management "quick start" guide for beginners, accidental, aspiring new agile project managers, and for those exploring agile project management careers or looking for a refresher.A process and an acronym will help the accidental agile project manager remember the essential steps of projects. It's Ray's PROJECT method: Chapter #1: The "P" - P is for People
Chapter #2: The "R" - R is for Requirements
Chapter #3: The "O" - O is for Organize
Chapter #4: The "J" - J is for Jell
Chapter #5: The "E" - E is for Execute
Chapter #6: The "C" - C is for Control
Chapter #7: The "T" - T is for TransferThe purpose of the PROJECT method is to get you started quickly, not make you an expert or teach you everything you need to know. This book is written as a business fable to help deliver the messages. It follows the method as it is applied to a fictional yet realistic organization and accidental agile project manager. This makes the character and the process more relatable and memorable to the reader.Each chapter is devoted to a step of the method and ends with "Knowledge Nuggets" - tips, basic project management templates, and references for further reading and study. References include sections of the Project Management Body of Knowledge (PMBOK(R) Guide), the Project Management Institute's (PMI) standards for project management, and Agile Practice Guide.Templates include: - Stakeholder Register
- Communications Plan
- Requirements Plan
- Requirements Document (User Stories)
- Product Backlog
- Milestone Plan
- Burndown Chart
- Virtual Team Contact
- Kickoff Agenda
- Lessons Learned
- Retrospective
- Status Report
- Team Member Evaluation
- Lessons LearnedAll templates are available online and ready-to-use with pre-filled examples.