Agile . Agile Agile Agile Cynefin Framework Spectrum of a Design Spectrum of a Design + suited for situations where change is uncommon (closed requirements projects) + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + customer/user/stakeholder interaction not so intensive + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + customer/user/stakeholder interaction not so intensive + can work with not-so-motivated, not-soskilled people + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + customer/user/stakeholder interaction not so intensive + can work with not-so-motivated, not-soskilled people + distributed knowledge not needed, specialization supported + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + customer/user/stakeholder interaction not so intensive + can work with not-so-motivated, not-soskilled people + distributed knowledge not needed, specialization supported + distributed teams not a problem + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + customer/user/stakeholder interaction not so intensive + can work with not-so-motivated, not-soskilled people + distributed knowledge not needed, specialization supported + distributed teams not a problem + focus on controlling + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + customer/user/stakeholder interaction not so intensive + can work with not-so-motivated, not-soskilled people + distributed knowledge not needed, specialization supported + distributed teams not a problem + focus on controlling + big design upfront not necessary + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + customer/user/stakeholder interaction not so intensive + can work with not-so-motivated, not-soskilled people + distributed knowledge not needed, specialization supported + distributed teams not a problem + focus on controlling + big design upfront not necessary + can deal with uncertainity, adpats to changes (customer requirements are hazy, the business environment is uncertain) + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + customer/user/stakeholder interaction not so intensive + can work with not-so-motivated, not-soskilled people + distributed knowledge not needed, specialization supported + distributed teams not a problem + focus on controlling + big design upfront not necessary + can deal with uncertainity, adpats to changes (customer requirements are hazy, the business environment is uncertain) + change is embraced + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + customer/user/stakeholder interaction not so intensive + can work with not-so-motivated, not-soskilled people + distributed knowledge not needed, specialization supported + distributed teams not a problem + focus on controlling + big design upfront not necessary + can deal with uncertainity, adpats to changes (customer requirements are hazy, the business environment is uncertain) + change is embraced + better for projects, where success is measured by business value deliver + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + customer/user/stakeholder interaction not so intensive + can work with not-so-motivated, not-soskilled people + distributed knowledge not needed, specialization supported + distributed teams not a problem + focus on controlling + big design upfront not necessary + can deal with uncertainity, adpats to changes (customer requirements are hazy, the business environment is uncertain) + change is embraced + better for projects, where success is measured by business value deliver + frequent working releases + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + customer/user/stakeholder interaction not so intensive + can work with not-so-motivated, not-soskilled people + distributed knowledge not needed, specialization supported + distributed teams not a problem + focus on controlling + big design upfront not necessary + can deal with uncertainity, adpats to changes (customer requirements are hazy, the business environment is uncertain) + change is embraced + better for projects, where success is measured by business value deliver + frequent working releases + intensive collaboration with customer + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + customer/user/stakeholder interaction not so intensive + can work with not-so-motivated, not-soskilled people + distributed knowledge not needed, specialization supported + distributed teams not a problem + focus on controlling + big design upfront not necessary + can deal with uncertainity, adpats to changes (customer requirements are hazy, the business environment is uncertain) + change is embraced + better for projects, where success is measured by business value deliver + frequent working releases + intensive collaboration with customer + supports creativity a overlapping knowledge of employees + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + customer/user/stakeholder interaction not so intensive + can work with not-so-motivated, not-soskilled people + distributed knowledge not needed, specialization supported + distributed teams not a problem + focus on controlling + big design upfront not necessary + can deal with uncertainity, adpats to changes (customer requirements are hazy, the business environment is uncertain) + change is embraced + better for projects, where success is measured by business value deliver + frequent working releases + intensive collaboration with customer + supports creativity a overlapping knowledge of employees + simple processes + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + customer/user/stakeholder interaction not so intensive + can work with not-so-motivated, not-soskilled people + distributed knowledge not needed, specialization supported + distributed teams not a problem + focus on controlling + big design upfront not necessary + can deal with uncertainity, adpats to changes (customer requirements are hazy, the business environment is uncertain) + change is embraced + better for projects, where success is measured by business value deliver + frequent working releases + intensive collaboration with customer + supports creativity a overlapping knowledge of employees + simple processes + transparency + suited for situations where change is uncommon (closed requirements projects) + suited for heavy engineering processes (medical, NASA) + suited for projects, where certificate is needed + suited for long release cycle + suited for contract driven deals (cheaper) + customer/user/stakeholder interaction not so intensive + can work with not-so-motivated, not-soskilled people + distributed knowledge not needed, specialization supported + distributed teams not a problem + focus on controlling + big design upfront not necessary + can deal with uncertainity, adpats to changes (customer requirements are hazy, the business environment is uncertain) + change is embraced + better for projects, where success is measured by business value deliver + frequent working releases + intensive collaboration with customer + supports creativity a overlapping knowledge of employees + simple processes + transparency + focus on empowerment Product Owner 68% PM PM + Lean PM + Lean = PO PM + Lean = PO Wind Freaks Tools Vision Board Simon Sinek Personas User Stories As a [role] I want to [do some action] so that [business value] As an editor I want to add a new spot so that I can share info about a new location F.A.A.R.T. A.A.R.T. As an editor I want to add a new spot so that I can share info about a new location Max adds a new spot to share info about a new location. Max adds a new spot to share info about a new location. Max records his trip to share tips and inspire others. Max adds a new spot to share info about a new location. Max records his trip to share tips and inspire others. - visited spots on a timeline Max adds a new spot to share info about a new location. Max records his trip to share tips and inspire others. - visited spots on a timeline - article about the trip Max adds a new spot to share info about a new location. Max records his trip to share tips and inspire others. - visited spots on a timeline - article about the trip - integration with Trip Journal app Backlog Max adds a new spot. Max adds a new spot. Max records his trip. Vision Board Personas Vision Board User Stories Personas Vision Board User Stories Personas Vision Board Backlog Emergent Iterative Discovery Iterative Discovery Iterative Discovery Iterative Discovery Iterative Discovery Activities 50% 50% Users Users Customers Users Customers Stakeholders Product Ownership in a Nutshel UX Skills Communication (Guts to say) No Incremental Thinking Max records his trip to share tips and inspire others. Max records his trip to share tips and inspire others. Pareto 80% 20% - visited spots on a timeline - article about the trip - integration with Trip Journal app Max records his trip to share tips and inspire others. - visited spots on a timeline - article about the trip - integration with Trip Journal app Max records his trip to share tips and inspire others. Max writes article about his trip to inspire others. - links to from spots to the article Any intelligent fool can make things bigger, more complex and more violent. It takes a touch of genius and a lot of courage to move in the opposite direction. http://bit.ly/nikdo-agile @nikdo