by Stelian Roman
September 24, 2021 |
60:15 |
Views: 7,761 |
PDUs: 1.00 |
Rating: 4.57 / 5
‘Scaled Agile’ is one of the most misunderstood concepts. Agile adoption surveys indicate that Scrum, or some combination of it, is used by 70--80% of Agile Teams. None of the 'scaled' frameworks is mentioned as 'used', only as an option to 'scale'. Agile, a new approach in 1970 to scale down manufacturing processes and make them more ‘Agile,’ was created to improve Lean Six Sigma. Out of Software development, the team frameworks are now 'scaling up' by reverting to Lean Practices like Kanban, Theory of Constraints, Voice of Customer, Kaizen, etc. The Six Sigma component that is the most mature and confirmed way of measuring the impact of process improvement initiatives was left out. This is possibly partly because it requires skills and knowledge that can't be acquired in a 2-3 days course, partly because its practices are associated with manufacturing, and it is as seen incompatible with software development. In addition, Lean goals (eliminate waste, adoption of standardized processes) are completely opposed to the Agile mindset that fundamentally embraces change, allows good waste, and is against reliance on standardized processes, This webinar is an analysis of lessons learned from using Lean Six Sigma to measure process improvement initiatives in software development including a comparison between Agile and Planned approaches in a large system development. It is a project manager's view that is probably different than what is heard in conferences and training courses.