Agile Project Management with Scrum
The rules and practices for Scrum-a simple process for managing complex projects-are few, straightforward, and easy to learn. But Scrum's simplicity itself-its lack of prescription-can be disarming, and new practitioners often find themselves reverting to old project management habits and tools...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Sebastopol :
Microsoft Press
2009.
|
| Edición: | 1st edition |
| Colección: | Safari tech books online.
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627189106719 |
Tabla de Contenidos:
- Agile Project Management with Scrum; Foreword: Why Scrum Works; Acknowledgments; Introduction; 1. Backdrop: The Science of Scrum; Complex Software Development; The Skeleton and Heart of Scrum; Scrum Roles; Scrum Flow; Scrum Artifacts; Sprint Backlog; Increment of Potentially Shippable Product Functionality; Summary; 2. New Management Responsibilities; The ScrumMaster in Action; The ScrumMaster's Value; The Product Owner at MegaEnergy; The Product Owner in Action; The Product Owner's Value; The Team at Service1st; The Team in Action; The Team's Value; Conclusions; 3. The ScrumMaster
- Lessons LearnedThe Untrained ScrumMaster at Litware; Lessons Learned; Overzealous at Contoso.com; Lessons Learned; Wolves at MegaFund; Lessons Learned; Conclusions; 4. Bringing Order from Chaos; Lessons Learned; The Situation at Tree Business Publishing; Lessons Learned; The Situation at Lapsec; Lessons Learned; Conclusions; 5. The Product Owner; Getting Service1st's Management Back in Action; Lessons Learned; Fixing the Problem of XFlow at MegaFund; Lessons Learned; Company Goals at TechCore; Lessons Learned; Company Goals at MegaBank Funds Transfer System; Lessons Learned; Conclusions
- 6. Planning a Scrum ProjectWhat Does ""Done"" Mean?; How Hard It Is to Change; Lessons Learned; Certified ScrumMasters Take on Return on Investment (ROI); Product Backlog; The Project; Uh-Oh!; What Advice Should You Provide?; How the Teams Respond to This Exercise; Team 2's Advice; Team 3's Advice; Team 4's Advice; Lessons Learned; Conclusions; 7. Project Reporting-Keeping Everything Visible; Lessons Learned; Getting More Information at MegaBank; Lessons Learned; Not Everything Is Visible at Service1st; Lessons Learned; Conclusions; 8. The Team; Learning to Engineer Better: The Transition
- Learning to Self-Organize: The TransitionEstimating Workload: The Transition; What Happens If Actuals Are Compared to Estimates; Lessons Learned; Learning to Have Fun While Working: The Transition; Giving the Team a Chance at WebNewSite; Lessons Learned; Conclusions; 9. Scaling Projects Using Scrum; Lessons Learned; Scrum Scaling; Scaling at Medcinsoft; Bug Fixing; Lessons Learned; Conclusions; A. Rules; Daily Scrum Meeting; Sprint; Sprint Review Meeting; Sprint Retrospective Meeting; B. Definitions; C. Resources; D. Fixed-Price, Fixed-Date Contracts; How to Ignore Competitive Advantage
- E. Capability Maturity Model (CMM)SEI, CMM, and Scrum; Ken Schwaber; Index
