Hands-On at ISEP DEI | 18th of Feb 2017
•Download as PPTX, PDF•
0 likes•156 views
Company Z is struggling to satisfy customers and losing money due to low delivery pace and missed deadlines. Their product requirements are constantly changing, and work passes through multiple teams without clear planning or forecasting. This has led to tension between teams and poor behaviors. The document proposes establishing KPIs, analyzing team workflows, coaching management to restructure cross-functional teams, and mentoring the teams in continuous improvement principles and identifying improvement actions based on data.
More Related Content
Similar to Hands-On at ISEP DEI | 18th of Feb 2017
Similar to Hands-On at ISEP DEI | 18th of Feb 2017 (20)
More from Eduardo Ribeiro
More from Eduardo Ribeiro (13)
Recently uploaded
Recently uploaded (20)
Hands-On at ISEP DEI | 18th of Feb 2017
- 1. Hands-On Continuous Improvement and Advantages (Scrum/Kanban/Scrumban) by Eduardo Ribeiro V 2.0
- 7. Company Z • Company Z is struggling to satisfy their customers. • Their teams are delivering with quality still they deliver at a low pace making them miss the deliveries dates (Target Dates). • The bigger issue is that due to this Company Z is losing costumers trust what is affecting their stocks in the stock market.
- 8. Closer look • Product it’s constantly changing and pushing their new requests to the teams. • Sometimes there are implementations that are not accordantly with what was requested. • Every work item must pass through different teams (Different Skills). • Deployment is made when the team finish the full request. • Teams are unable to forecast when a new request can be implemented and deployed. • Due to the constant delay, teams change size often to respond to the bad planning. • As we speak there is allot of tension between everyone creating each day more noise and bad behaviors.
- 11. My way • Establish KPI’s to have data as starting point. • After analyzing the data, observe how the teams are working and identify issues/improvement points. • Share my discoveries with the teams and top management. • Coach Top Management to reorganize the teams (Cross- Functional Teams). • Coach and mentor the new teams including embedding the Continuous Improvement principles and values. • Observe how the teams are now working and identify issues/improvement points. • Work with the teams to review all the data and help them to generate and follow the actions to improve. • Help the teams to identify tools to help them to continuously improve. • Keep observing how the teams working/improving. • Do some follow-up sessions.
Editor's Notes
- “Agile is an “iterative” and “incremental” software development methodology were its main focus is on client satisfaction through continuous delivery.” In other words build the highest value software, with high quality, as quickly as possible. A software / product development methodology: Fast Adaptive Respond to change Self organizing, self motivated, multi functional, Empowered teams. Requirements are captured in small items in a list of “Product Backlog”. Traditional -> 50% completed we have 0% usable. Agile -> 25% completed we have 100% usable. We have a continuous feedback every iteration/increment and having the change to keep improving our products by redefining the “Product Backlog”.
- Lean Software Development Extreme Programming (XP) Kanban Feature Driven Development (FDD) Behavior Driven Development (BDD) Crystal Clear Scrumban
- Talk about Continuous Improvement and advantages.
- This is a real scenario that I encountered a few months ago and I would like you to think out side the box and came with tools to analyze what could be improved and possible solutions to solve the problem.