Agile at enterprice level

Editor's Notes

1. Before you could say read the fucking manual. If today you still need manual you’re out of business It’s about another level of service IT has to provide. Business knows the price & speed at which you can rent storage at amazon and they demand the same level of service. App market? There is abundance of software. They aim is not longer to make software, nor to sell software just to get your free app used by a customer… Differentiator? added value for the user. Remark that added value is not only functionality but can be – and is more and more - design as well.
2. Promise of agile: More business value faster
3. The difficulty of Agile is in values, principles and Attitude.
4. Close the part with putting in production. Collaboration is not enough. Tools is nessesary e.g. testautomation, deployment…
5. From agile team/project to agile company/IT Less: Large scale scrum Dad: Disciplined agile delivery SAFe: Scaled agile framework In common Combine Lean & Agile Basic component: scrum team recurcivity
6. Goal: decisions are taken at the right level: Priority of epics is decided at portfolio/epic level: not to be discussed further on – as a guidance for the other levels Priority of features in PSI: decided on program/feature level … Combine Agile & lean
7. Presence: everybody of the release train (organize yourselves!) Organizer: ING IT Integrator or IT Integrator Start with context (PPM), Roadmap en Architectore ING termen: Investment them committee, program manager, feature owner en it integrator ipv Program Portfolio management, Epic owner, Program manager and release train engineer
8. EO, EA, RTE and PPM are present for questions SoS each hour (SM, PO an program level)
9. Outcome for a team: PSI objectives (PO gives bus. Value (with PPM and Product Manager (CPO)) Risks and impediments per team
10. Features: so when a feature as a whole is delivered Yellow: dependent feature input that need to be finished (by other teams) in order to deliver the features Place of the post-its does not say anything of when a team starts with a feature or feature input. Line: features with input: features to be developed by different teams, with dependencies (for each team)
11. Slice the work in small pieces. Make a card for each of these pieces.
12. Draw columns for each of the process steps.
13. Stick the cards in the columns.
14. And pull the work items through the process steps. It’s visual, simple and improves shared understanding.
15. Put a limit on the number of work items that can live in a column. This limit is called the W.I.P. limit, Work-In-Progress limit.
16. Prevent overload. Avoid to start many but to finish few. Avoid task switching. Increase focus.
17. Decrease lead time. Enable fast feedback.
18. Identify bottlenecks. And hence improve flow.
19. Measure lead time.
20. Class of service
21. Definition of done
22. Job sequencing algorithm If you only quantify one thing, quantify the cost of delay
23. How do you prioritize epic and feature backlogs?
24. Cost of delay Duration => job size Ratio of business value over effort size Business value => value to user or business; time criticality to user or business; … => opportunity cost to delay implementation => cost of delay Effort size => duration
25. Cost of delay Duration => job size Ratio of business value over effort size Business value => value to user or business; time criticality to user or business; … => opportunity cost to delay implementation => cost of delay Effort size => duration
26. Example: fashion
27. Example: process automation
28. Cost of delay Duration => job size Ratio of business value over effort size Business value => value to user or business; time criticality to user or business; … => opportunity cost to delay implementation => cost of delay Effort size => duration
29. Cost of delay Duration => job size Ratio of business value over effort size Business value => value to user or business; time criticality to user or business; … => opportunity cost to delay implementation => cost of delay Effort size => duration
30. Controversy around scaling in agile community: Culture for value creation and speed?: free market. They produce more and faster then people can follow. Companies adore it and ask less government, less rules, less administration in order to speed up. Basically: get out of the way of companies who want to work, that is how added value is created. By contract there is no added value create : how the western world sees communism with their central and planned economy wand lots of control. They needed to build a wall to keep people inside. Strange: external, organizations want free market, internal organization of companies is more like... Feedback from people in bigger companies: less governance, less rules, less administration get out of the way of people who want to work that is how added value is created. Fundamental remark from agile community: you can turn a blue triangle into a green one but it remains a triangle. Agile is going to another type of organisation like adhocraty, network organisation, innovative ecosystems… My conclusion: there will be a case against scaling in 5-10 years time for the bigger companies. You can’t go from a blue triangle to a green circle directly (evolution not revolution.) From talking about agile (triangle) to being agile e.g. Spotiy: by the time the structure is described it has changed. (tip as long as you have reorganisations you have planned change
31. All Disiplines are done one after another Business involvement is high in the beginning and the end of te project