Agile Mëtteg - 22 September 2011.
In Luxembourg we see many IT teams that are struggling to respond to new business requests while supporting existing systems. Without a proper management framework and clearly defined objectives, this can lead to misunderstanding between business and IT, and eventually disappointment and distrust.
In the past few years a new approach has emerged within the Lean/Agile community: Kanban for software development. This method differentiates from most other Agile approaches as it is not iterative but based on a continuous flow managed with a pull system.
During this session you will discover the Kanban Method and how to implement it for empowering your team for managing both software development projects and support activities, achieving better results and rebuilding trust with your business stakeholders.
5. OUR SERVICES 22 September 2011 Agile Mëtteg – Kanban 5 MgtTeamServices Dedicated for IT, Business and Operational organizations 4 Software Development 1 Development offast & flexible solutions business value oriented enabling productivity maximizing ROI Training and Consulting helping understanding and applying Agility making available easy and powerful tools for follow-up of relevant KPI adopting and deploying Simple & pragmatic methods for achievements of project objectives Agility Agility OpsTeamServices Dev Team Services 2 3 2 1 3 Agility 4 Based on values and principles of Agility
6. OUR MEANS 22 September 2011 Agile Mëtteg – Kanban 6 Overall seniority 80% > 4 years 56% > 8 years 31% > 12 years Long term collaboration 100% trust us after a first mission Authorized Training Centerin Luxembourg Agility We partner with IT and agile actors when relevant
9. PARTICIPANTS ABOUT YOU… Who are you? What is your role? What do you know about agility? 22 September 2011 9 Agile Mëtteg – Kanban
10. Robby is an IT manager, responsible for a development / support team He just took a new position and feels that trust needs to be rebuilt with the business stakeholders 22 September 2011 Agile Mëtteg – Kanban 10
12. He has heard about Agile methods like Scrum and Kanban But he wonders which approach would fit best to his particular context 22 September 2011 Agile Mëtteg – Kanban 12
14. AGILE COMMONALITIES Limit work in progress to capacity Deliver often (reduce time-to-market) Build quality in Continuously improve Visual management 22 September 2011 Agile Mëtteg – Kanban 14
22. SCRUM or KANBAN? …But what if work is so unpredictable that it cannot be possible to freeze scope of work for 2 weeks (which is typical for dev/support teams)? 22 September 2011 Agile Mëtteg – Kanban 22
28. KEY CONCEPTS Lean Pull Scheduling Systems Value Stream Mapping & Process Policies Input Cadence On-demand prioritization and predictable lead time WIP Limits Negotiated, 1 to 3 items per person / pair SLA and Predictability Classes of service Reporting & Metrics Lead time, due date performance, CFD Improvements Bottlenecks, waste elimination, reduction of variability 22 September 2011 Agile Mëtteg – Kanban 28
33. NEXT TRAININGS & EVENTS 22 September 2011 Agile Mëtteg – Kanban 33 Agile Mëtteg - Next free lunch seminar 20 October 2011: (TBD) http://www.agilepartner.net/category/free-seminars/ Complete calendar on: http://www.agilepartner.net/category/training-calendar/
34. CONTACTS Thank You 22 September 2011 Agile Mëtteg – Kanban 34 Follow us on:
Notes de l'éditeur
Story of Robby (IT guy, responsible for a dev/support team) whose attention has been caught by Agile in particular for rebuilding trust with its business stakeholders.
He considers Scrum and Kanban
In Scrum we use iterations (timebox and fixed scope)…
…but what if work is so unpredictable that it cannot be possible to freeze scope of work for 2 weeks (which is typical for dev/support teams)?
In Kanban we focus on the flow and limit WIP in the system at every moment in time