Your SlideShare is downloading. ×
  • Like
ScrumDay DK 2014: Scrum, kanban, prince2, dos and donts
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

ScrumDay DK 2014: Scrum, kanban, prince2, dos and donts

  • 266 views
Published

When combining Scrum with Kanban or Prince2, what to do and what not to do.

When combining Scrum with Kanban or Prince2, what to do and what not to do.

Published in Software , Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
266
On SlideShare
0
From Embeds
0
Number of Embeds
6

Actions

Shares
Downloads
6
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Scrum, Kanban & Prince 2 dos and don’ts Mads Troels Hansen Scrumday Denmark, June 17th 2014 @MadsTH, mth@lean-agile.dk
  • 2. ?
  • 3. Self Organization - Bottom up knowledge Values & principles Transparency InspectionAdaptation
  • 4. Thinking Empirical not Predictive Discovery Delivery
  • 5. Kanban – Kanban Method
  • 6. Kanban (1) http://en.wikipedia.org/wiki/Kanban Kanban (かんばん(看板) is a scheduling system for Lean and just-in-time (JIT) production1 Scrum: Manage complex work • Organizing for value Kanban: Manage complicated work • Organizing for flow Delivery vs. Discovery Kanban (System) Predictive vs. Empirical
  • 7. Kanban Method Foundational Principles • Start with what you do now • Agree to pursue evolutionary change • Initially, respect current roles, responsibilities & job titles • Encourage acts of leadership at all levels Core Practices • Visualise • Limit work in progress (WIP) • Manage Flow • Make Process Policies Explicit • Implement feedback loops • Improve collaboratively, evolve experimentally Source: http://www.leankanbanuniversity.com/kanban-method
  • 8. Case: Using the Kanban Method Team not using Scrum • Board visualizing work • A team • A facilitator in the team • WIP limit on people in the team • Backlog with a owner • Daily stand-up meeting • Definition of Done • Ready state • Agreed on how to manage requests • Retrospectives biweekly
  • 9. • More about “Change Management” • Incremental Change Kanban Method You don’t change to the Kanban Method Delivery vs. Discovery Predictive vs. Empirical
  • 10. Prince2 More by Brett Maytom (PST), Youtube video: http://bit.ly/1n2CECk
  • 11. Prince2 http://en.wikipedia.org/wiki/PRINCE2 PRojects IN Controlled Environments 7 principles - 7 Themes - 7 Processes
  • 12. Prince2 http://en.wikipedia.org/wiki/PRINCE2 Scrum Scrum Scrum Scrum Scrum Scrum Scrum Delivery vs. Discovery Predictive vs. Empirical
  • 13. Delivery vs. Discovery Predictive vs. Empirical
  • 14. Summary You don’t change to the Kanban Method Delivery vs. DiscoveryPredictive Empirical When applying tactics and processes with Scrum 2014, Mads Troels Hansen (@MadsTH)www.Teamdriven.dk A kanban system alone is more about delivery and flow Scrum in Prince2 is NOT only about delivery