Agile concepts for quality and process engineers for slideshare
6 likes1,876 views
This document contains information about Yuval Yeret, including that he is the CTO of AgileSparks and a Kanban/Agile consultant. It discusses various Agile and Lean concepts like embracing uncertainty, delivering value through working software frequently, empowering teams, and adapting processes through retrospectives. The document advocates applying Agile principles not just to products but also to how teams work and emphasizes the need to consider context when selecting practices.
Ad
More Related Content
What's hot (20)
Viewers also liked (20)
Ad
Similar to Agile concepts for quality and process engineers for slideshare (20)
Ad
More from Yuval Yeret (20)
Agile concepts for quality and process engineers for slideshare
- 2. About Me • CTO & Senior Kanban/Agile Consultant @ www.AgileSparks.com • Blogging at http://YuvalYeret.com • Author of Holy Land Kanban https://leanpub.com/holylandkanbanbestof
- 3. Nothing is certain anymore… Where are your projects ? http://www.derailleurconsulting.com/blog/complexity-and-noise-in-systems-development-projects
- 4. We need approaches that embrace uncertainty/complexity and the speed of the 21st century http://www.derailleurconsulting.com/blog/complexity-and-noise-in-systems-development-projects This uncertainty applies not just to what we are creating, but not less importantly to the way we are working…
- 5. We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value : While there is value in the terms on the right We value the items on the left more )http://www.agilemanifesto.org) Process and tools Individuals and interactions over Comprehensive documentation Working software over Following a plan Responding to change over Contract negotiation Customer collaboration over The agile paradigm supported by these values applies not just to what we are creating, but not less importantly to the way we are working…
- 6. Principles behind the Agile Manifesto • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. • Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. • Business people and developers must work together daily throughout the project. • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. • Working software is the primary measure of progress. • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. • Continuous attention to technical excellence and good design enhances agility. • Simplicity--the art of maximizing the amount of work not done--is essential. • The best architectures, requirements, and designs emerge from self- organizing teams. • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Use Agile principles for designing the way of working as well
- 7. ”Vertical” increments! Henrik Kniberg Structure Tech/Infrastructure Metrics 1 5 2 3 1 4 3 2 value “Vertical” increments of “Methodology” / Way of working, not just the Product! Sometimes called “Minimum Viable Change/Method”
- 8. Focus on (Method) Feedback! Delivery frequency = Speed of learning Henrik Kniberg Feedback and Requests Demos and Releases Method Development team Employees &Stakeholders It is not the strongest species that survive, nor the most intelligent, but the ones most responsive to change. Charles Darwin
- 9. History of key Lean/Agile Frameworks Kanban – 2010s Evolve into Lean/ Agile Focus on the flow Scrum – 2000s Jump into Lean/Agile Still the leading classic agile approach Extreme Programming – 90s Lean/Agile Engineering practices Bring in the right practices at the right time, but ignore at your own risk! These are Agile Frameworks/Methods, NOT Methodologies. They guide you using Lean/Agile principles/values/practices towards the process best fit to your reality. Each of them incorporate learning/adaptation aspects
- 10. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.” Agile Manifesto principle
- 11. The Retrospective in Scrum & Kanban • In Scrum – do it every Sprint/Iteration – Interesting fact: Initially the Retrospective wasn’t part of Scrum. Optimizing the process wasn’t part of the guidelines. Most agile consultants/ practitioners are not aware of it since they see Retrospective as such a core aspect of Scrum/ Agile • In Kanban – create a rhythm/cadence of retrospectives similar to Scrum, or do it when issues accumulate – A key kanban practice is “Implement Feedback Loops” where the retrospective is a key one. The “Operations Review” is another.
- 12. Align people on the vision/direction & then Decentralize what you can Give people more authority in decisions regarding the work AND the way of working The biology of bottlenecking. (From Leaders Eat Last by Simon Sinek)
- 13. Changes that Agile will drive: • Infrastructure Investments (release automation, test automation, etc) • Evolve the organizational (new roles, cross-functional teams, etc) • New skills (Vertical story-slicing, agile architecture, XP engineering practices, retrospectives, etc) • New habits (Frequent customer interaction, frequent release, less specialization) • Transparency (problems and uncertainty painfully visible rather than hidden) Henrik Kniberg What will happen if we don’t do this? But no need to do it all at once
- 15. #TechSafety/#Anzeneering consider these common injuries to software makers: • Alteration Anxiety: apprehensive uneasiness associated with making changes • Antique Agony: mental anguish from working with old technology • Brain Hernia: straining your brain to understand code with high conceptual weight • Fractured Flow: feeling interrupted causing an inability to focus • Fragility Frustration: dissatisfaction with that which is easily and perpetually broken • Merge Misery: suffering caused by difficult merges of code • Release Rage: exhausting, manual release to production that robs one of family time, sleep, joy • Schedule Stress: tension associated with a deadline http://www.industriallogic.com/blog/techsafety/ TechSafety is about protecting people as a core habit that drives cultural change - Protecting people underlies every Lean or Agile practice. Reduce Technical Debt, Maintain Sustainable Pace, Empower people, Continuous Integration, etc.
- 16. Sustainable Pace Manifesto Pulling work & going home happy with today’s amount & quality of work Delivering working scope Having a profitable bottom line for the whole project Finding the time to fine-tune the way we work Pushing for meeting arbitrary unrealistic due dates Delivering 100% of scope Meeting construct budget Focusing JUST on day to day activities Over We Value: Meaning: While there is value in the items on the right, we value the items on the left more. From one of AgileSparks’s clients…
- 17. http://www.agilesparks.com/AS%20Way Agile Change Management – Changing towards agile
- 18. Evolution & Revolution Evolution? Revolution? It depends. We also see a pattern of starting with Evolution and shifting to revolution once a “glass ceiling” is reached. See http://www.agilesparks.com/starting-product-stream-kanban for example
- 19. A key principle - It Depends… Don Reinertsen - Six Myths of Product Development – Harvard Business Review_2012-05
- 20. Most IT/Product Development shops are complex systems • Which means we CANNOT have one Best Practice • We have “Good Practices” but we need to probe & sense to see if they fit or if we need a new emerging practice Cynefin framework by Snowden / Cognitive Edge https://www.youtube.com/watch?v=N7oz366X0-8
- 21. Should we have “A Methodology?” • Yes – there is benefit in shared language, “full kit” enabling faster roll-out, especially when there is commonality between contexts • Identify best practices that apply everywhere • Identify good practices and the what are the considerations to choose them • Design for inspect/adapt – help the right practices for the context to emerge
- 22. 5. Build & Deployment 1. Continuous Integration – automatic build running at least nightly 2. All code and artifacts are versioned using a single scheme 3. Build is trigged automatically upon code checked in 4. Automated regression tests run as part of build and give a green/red binary answer (no need for analysis to determine success/failure) 5. Frequent check-ins to common branch 6. Build failures are addressed immediately. Repeated build failures trigger a stop the line event 3. Individuals & Interactions Feedback Loops 1. All people involved in a work item work on it more or less in the same time period (Developers, Testers, Functional/ Product) minimizing the overhead/waste from context switching/recalling past work. 2. All people involved in a work item (even across silos) can collaborate directly with each other without third parties like team leads in every coordination/communication loop enabling faster decisions and more scalable operation. 3. People working together act as a team with shared accountability to end to end delivery thereby decisions are more value than silo-focused 4. Significant aspects of goals and rewards are oriented towards team performance/goals (rather than individual performance) driving collaboration not just individualism. 5. Team environment is as collaboration friendly as possible 6. Individuals are involved in performance feedback of the people they are working with, to encourage teamwork 4. Engineering Practices 1. There is a clear definition of what "Coding Done" means and people are working according to it 2. People are expected to write SOLID/CLEAN code and estimations reflect it 3. Automation coverage is planned and implemented as an integral part of production code implementation 4. Defects created as part of new development are fixed as early as possible and in any case before considering that work item as done 5. There is a Test Automation Pyramid strategy guiding Automation coverage decisions (Preference to Unit Tests>>API tests>>UI tests) 6. People are expected to refactor smelly code as part of "Coding Done“ and estimations reflect it 7. Functional Design is specified Test-Driven (ATDD/BDD) 8. Sustained or improved code coverage is verified at build time using code coverage analysis tools (e.g. Sonar) 9. Team is pro-actively and methodically improving collective ownership 10. All code is reviewed in small batches, gaps are closed within hours 11. People have access to the tools they need to do effective SW engineering 12. A prioritized backlog of Technical Debt (ugly code, missing tests, etc.) is available and capacity is allocated to reducing it 13. Team maintains a high level of Collective ownership - most tasks can be pulled by many members of the team without a major effect on efficiency 14. Technical Code Design is Test-Driven (TDD) 15. Regression cycle costs days at most (due to high level of automation) 6. Empowered Teams and Individuals 1. Daily planning meetings (a.k.a. Standups) are used by people to manage their day to day work (instead of work scheduled by supervisors and pushed onto them) 2. Autonomy - People have a high degree of control over the project day 2 day execution - Choose tasks to pull, where to focus 3. Reason/Intent is communicated as part of every requirement/work item, to increase motivation as well as empower people to do the right thing for the context rather than blindly follow a plan 4. People pull to capacity - by using Team Estimation approaches or just pull to WIP 5. Autonomy - People have a high degree of control over their personal & professional destiny 6. The behavior that is incentivized (formally and informally) is aligned with lean/agile thinking - Flow, Improvement, Trust, Whole Team, Low WIP, Safe to fail experiments, etc. 7. People work in small teams (not more than 10, ideally around 5-7) enabling good communication and direct collaboration as well as effective meetings and interaction 8. Managers are pro-actively and methodically seeking ways to improve autonomy of teams and individuals as a way to enable faster decisions as well as higher engagement/motivation 9. People are given opportunity to improve their mastery of areas which interest them 10. People can shape their work environment – technologies, facilities, etc. 2. Business Value Driven Development 1. Product owner sees working software frequently and uses the feedback to adapt the scope/timeline plan 2. Work items are integrative and testable cross-cutting across the architecture if necessary (e.g. User Stories). Done = Deployable and Performant/Secure, enabling real feedback/ learning. 3. Work items are integrative testable & SMALL - can be delivered in days thereby tightening the internal team level feedback loop 4. frequent feedback from stakeholders/users is used to adapt the scope/timeline closing a real feedback beyond the product owner. 5. Escaping Defects and other kinds of Failure Demand (Waste) are analyzed using Five Whys or another kind of root cause analysis process in order to determine reasons for missing them earlier in the process. 6. Value is delivered in iterative chunks using Minimally Marketable Features (MMFs) thereby achieving business agility – faster time to market and keeping more options open to what will be delivered after the current MMFs. 7. Requirements that are Hypothesis are validated Using MVP/MVF in a fast learning loop that includes Beta/Early Access programs or Continuous Delivery, in order to enable safe/cheap- to-fail experiments about risky but worthy ideas. 8. Feature Usefulness and Successfulness is evaluated as part of the development lifecycle. Learning is applied to improve the feature and future ideas. 9. Frequent Delivery to real users - up to 8 weeks apart 10. Continuous Delivery - work items are deployed/activated/validated as part of the work life cycle - in a matter of hours/days thereby minimizing the work done without feedback that it is in the right direction 1. Visualize & Manage the Flow 1. Visualize main Work types (using Kanban Board or similar) to create flow awareness 2. Definition of what Done (Working Tested Software) means is clear and adhered to (“DoD”) so real flow is measured and so exceptions drive discussion/improvement. 3. Visualize who is working on what in order to be aware of level of multi tasking and dependency on specific people. 4. Commitment to finishing work over starting new (eventually reaching a WIP level that “feels OK” for the team) to start to “weakly” constrain and improve flow. 5. Use flow diagrams/charts (e.g. CFDs) to provide predictability and insight into flow 6. Visualize and focus on blocked work so major flow efficiency issues are addressed 7. Visualize work that is queued/waiting between people/workflow states to start raise to awareness reasons for queuing and identify options for reducing 8. Awareness of Work Types and Work Items and differences in handling, in order to enable expectation setting with different stakeholders for different needs & allow people to make intelligent flow decisions according to the context 9. Some areas in the flow have local work in process (WIP) limits - leading to lower WIP and cycle times and more explicit opportunities to learn from the (lack of) flow 10. Visualize work variability and seek to reduce it (e.g. using Cycle Time Control Charts) so that overall average cycle time is improved and there is less uncertainty about velocity/cycle times enabling more aggressive planning 11. Explicit WIP limit at workflow level - Single workflow full pull – catching more flow problems and driving WIP/cycle time even lower. 12. Next is re-prioritized continuously (no commitment in Next)- Deferred Pull decisions (dynamic prioritization) in order to enable business agility. 13. Definition of what “Ready for work” means is clear and adhered to in order to minimize rework or blocks due to unready work occupying the WIP. 14. Guidelines for how to pull work (selection from ‘Next’/prioritization of WIP) are clear to everyone and adhered to so that most decisions can be decentralized and made faster as well as driving discussion about how to work and resulting in experiments/improvements 15. Capacity is allocated to Investment Themes using work in process limits so that it is possible to ensure certain investment in each theme. 7. Improve 1. Regular Lessons Learned events (frequency of no less than every 1-4 weeks) with actionable outcomes (e.g. Retrospectives/Kaizen) 2. People at all levels are highly aware and involved in improvement activity 3. Actionable Improvement Work is visualized and managed using “Stop starting start finishing” 4. Leaders are aware of the current operational capabilities (may require metrics) 5. Leaders have an operational capabilities goal 6. Team/Group knows the current process challenge they are targeting 7. Team/Group knows what obstacles are preventing them from overcoming the current process challenge, what is currently being addressed and how 8. Team/Group allocates capacity/time slots for improvement work 9. Team/Group uses models to look at their condition and suggest experiments Agile Depth Team: Sky1 Date: Sep 2013 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 2 3 4 56 7 1 6 4 3 4 2 2 1 http://www.slideshare.net/yyeret/leanagile-depth-assessment
- 23. See Kent Beck’s idea as described by Markus Gartner at Leverage the friction/pain to drive/focus improvement efforts
- 24. Successful Agility at Scale requires Leadership • Real impact/improvement requires going beyond the team practices. Scaling and shifting the culture/mindset requires understanding, buy-in and engagement by leaders, in a way most companies have not achieved yet. • Look at: – Spotify Engineering Culture – Principles of Lean/Agile Leadership – Dean Leffingwell – Pull based change – Open Agile Adoption (Dan Mezick) – Start with Agile – Managers First (me) http://www.agilesparks.com/leanagile-management-list
- 25. A possible role for the Quality/Process engineer - Helping people along • Pass the knowledge about the method • Pass the knowledge about the change approach – inspect & adapt • Help people choose good practices for them and build the skills for making good choices in the future – they should understand the tradeoffs/ decision filters • Help deal with wicked problems – help new practices emerge, suggest good practices unknown to the organization • Enable people to continue their process improvement journey themselves
- 26. To summarize, Agile CAN fail, if you: • Go for it without a good reason/motivation or without communicating the purpose to people • Choose the wrong implementation approach for your humane and technological context • Expect it to happen auto-magically instead of requiring investment, attention, leadership • Expect it to deliver results without any changes to culture/capabilities/way things are done at all levels • Expect it to happen in a single linear big planning up front fashion • Do it without the right knowledge/experience/ guidance appropriate for your situation. (A legacy enterprise != small fresh technology startup)
- 27. Agile WILL succeed, if you: • Start with the end in mind – Have a real clear purpose that everyone buys into • Take into account the humane and technological context and choose an appropriate implementation approach and keep inspecting and adapting along the way based on what really happens. • Prepare for investing time, money, and management attention • Welcome the need to change how things are done (at all levels) • Understand that it is an agile journey involving continuous planning and adjustment, safe to fail experiments, successes and small failures, and a lot of learning • Make sure you have the right people and/or the right help/ guidance to challenge you, inspire you, keep you safe, keep you focused, keep you confident you can make it.
- 28. Where to learn more: Http://AgileSparks.com/Resources
- 29. AgileSparks • Sparking Sustainable Delivery and Improvement Approaches that help organizations deliver more value while enjoying the journey • Inspire others to improve their way of working by helping them invite new exciting relevant and useful ways of thinking and doing into their context in a way that focuses on value and is sticky and sustainable • Public Training – Exposing the community to exciting new ways to improve work and creating the practitioner community to support introduction and usage of those approaches inside organizations • Planning, Training, On the job coaching and supporting improvement programs • Contact us at www.agilesparks.com or [email protected]