A healthy project requires clarity of project (what are we building), the customer (for whom are we building), the purpose (why are we building it), and of release schedules (when are we building it). But it doesn’t stop there, a healthy project requires a collaborative contract and structure, an understanding of what quality means, constant communication between the team and all other stakeholders, and an appreciation of the project’s trajectory.

How do we use adaptive planning techniques while still providing accurate progress status to our traditional PMO counterparts? Is it possible to make decisions at the last responsible moment and still satisfy our organization’s long lead time for planning and resources?

This video presents some practical ways to cope with the often irrational resistance that change can cause.

This tutorials discusses the “definition of done”, a way of focusing on business value while avoiding technical debt.It explains to Agile Scrum Masters and Project Managers how release decisions and tradeoffs are made, and how to avoid technical debt.

If Agile works, why isn’t everyone doing it? This presentation makes the argument that it comes down to trust and presents tools and examples of how to build trust among the various stakeholders involved.