Agile Project Management with Scrum by Schwaber, Ken -- Read -- Imperial Library of Trantor

Index

Agile Project Management with Scrum

Foreword Foreword: Why Scrum Works Acknowledgments Introduction 1. Backdrop: The Science of Scrum

Empirical Process Control Complex Software Development The Skeleton and Heart of Scrum Scrum Roles Scrum Flow Scrum Artifacts

Product Backlog Sprint Backlog Increment of Potentially Shippable Product Functionality

Summary

2. New Management Responsibilities

The ScrumMaster at MetaEco

The Situation at MetaEco The ScrumMaster in Action The ScrumMaster’s Value

The Product Owner at MegaEnergy

The Situation at MegaEnergy The Product Owner in Action The Product Owner’s Value

The Team at Service1st

The Situation at Service1st The Team in Action The Team’s Value

Conclusions

3. The ScrumMaster

The Untrained ScrumMaster at Trey Research

What Was Wrong Lessons Learned

The Untrained ScrumMaster at Litware

What Was Wrong Lessons Learned

Overzealous at Contoso.com

Being Right Isn’t Everything Lessons Learned

Wolves at MegaFund

The Wolves Strike Lessons Learned

Conclusions

4. Bringing Order from Chaos

The Situation at Service1st

Application of Scrum Lessons Learned

The Situation at Tree Business Publishing

Application of Scrum Lessons Learned

The Situation at Lapsec

Application of Scrum Lessons Learned

Conclusions

5. The Product Owner

Customer and Team Collaboration Getting Service1st’s Management Back in Action

Sprint Review Meeting Lessons Learned

Fixing the Problem of XFlow at MegaFund

Addressing the Problem Lessons Learned

Company Goals at TechCore

How Scrum Helped TechCore Lessons Learned

Company Goals at MegaBank Funds Transfer System

How Scrum Helped FTS Lessons Learned

Conclusions

6. Planning a Scrum Project

Managing Cash at MegaBank

The Two-Day Sprint Planning Meeting

Estimating the Product Backlog What Does "Done" Mean? How Hard It Is to Change

Lessons Learned

Certified ScrumMasters Take on Return on Investment (ROI)

MLBTix

Project Plan

Project Background Product Backlog

The Project Uh-Oh! What Advice Should You Provide?

How the Teams Respond to This Exercise

Team 1’s Advice Team 2’s Advice Team 3’s Advice Team 4’s Advice

Lessons Learned

Conclusions

7. Project Reporting—Keeping Everything Visible

New Project Reporting at the MegaEnergy Title Project

Solving the Problem Lessons Learned

Getting More Information at MegaBank

Solving the Problem Lessons Learned

Not Everything Is Visible at Service1st

The Reality Lessons Learned

Conclusions

8. The Team

Team Formation at Service1st

Learning Who’s the Boss: The Transition

Lessons Learned

Learning to Engineer Better: The Transition

Lessons Learned

Learning to Self-Organize: The Transition

Lessons Learned

Estimating Workload: The Transition

How Estimates Improve with Scrum What Happens If Actuals Are Compared to Estimates Lessons Learned

Learning to Have Fun While Working: The Transition

Lessons Learned

Giving the Team a Chance at WebNewSite

Background Lessons Learned

Conclusions

9. Scaling Projects Using Scrum

Scaling at MegaFund

Approach Lessons Learned

Scrum Scaling Scaling at Medcinsoft

Approach Bug Fixing Lessons Learned

Conclusions

A. Rules

Sprint Planning Meeting Daily Scrum Meeting Sprint Sprint Review Meeting Sprint Retrospective Meeting

B. Definitions C. Resources D. Fixed-Price, Fixed-Date Contracts

How to Gain Competitive Advantage How to Ignore Competitive Advantage

E. Capability Maturity Model (CMM)

CMM at MegaFund SEI, CMM, and Scrum

Ken Schwaber Index

← Prev
Back
Next →

← Prev
Back
Next →