Trifork Group Ag · OMXCOP:TRIFOR
Trifork — Investor Presentation (2015)
24 slides from Trifork's investor presentation, 2015
Slide 1: Heart of Agile meets Risk Reduction 2.0 (Disciplined Learning)
“Heart of Agile” meets “Risk Reduction 2.0 (Disciplined Learning)” Dr. Alistair Cockburn http://Alistair.Cockburn.us ©Alistair Cockburn 2015
Slide 2: People ...
2 People ... Deciding … they don’t understand which keeps changing To an interpreter unforgiving of error Making decisions every decision has economic consequences and resources are limited. ©Alistair Cockburn 2015
Slide 3: The Agile Manifesto invites wimpy-ness
3 The Agile Manifesto invites wimpy-ness "… Individuals and interactions over processes & tools…" (Yayy!! I don't have to follow those stupid processes any more!) "… Working software over comprehensive documentation…" (W00t!! Dump the documentation! I LOVE this agile stuff!) "… Customer collaboratio
Slide 4: People develop skills in stages
4 People develop skills in 4 stages ©Alistair Cockburn 2015
Slide 5: The Heart of Agile simplifies again
5 The Heart of Agile simplifies again Deliver Collaborate Reflect Improve ©Alistair Cockburn 2015
Slide 6: The Heart expands into Details
6 The Heart expands into Details Social Technical Early Revenue Queues Business Cost Learning Income Goals Listen Collaboration Deliver Examine Step forward Results Collaborate Reflect Include Let someone Emotions else do it Trust Improve Introspect Focus Allow failure Forwards Experiment Change Lim
Slide 7: Advanced Agile Development
7 Advanced Agile Development Craft Professions skills in a medium Cooperative Game communication Flow Management teamwork unvalidated decisions strategies = inventory, lean processes Self-Awareness (Personalities) Knowledge Acquisition the people, strategies, techniques pay-to-learn actually used tr
Slide 8: Use Lean Processes for Flow Management
8 Use Lean Processes for Flow Management ©Alistair Cockburn 2015
Slide 9: In software development, people wait on other people to make decisions
9 In software development, people wait on other people to make decisions I wish they’d decide A decision made what style by the user/sponsor they want! Every to be used by the I wish they’d decide line of code UI designer on the UI design is a decision! already! (Think about UI how many lines Design
Slide 10: Software = manufacturing if Inventory = Decisions!
10 Software = manufacturing if Inventory = Decisions! UI Designers Users & Sponsors Programmers Testers Business Analysts ©Alistair Cockburn 2015
Slide 11: A team's optimal process depends on its decision dependency network
11 A team’s optimal process and best strategies depend on its decision dependency network. UI Designer Enough Users Lots of & Sponsors Programmers Single, solitary A few Database Business Analysts designer Enough Users & Sponsors Not enough Programmers Some Many Testers Business Analysts UI Designer
Slide 12: Large-batch transfers make a system's behavior harder to predict
12 Large-batch transfers (of decisions, in our case ) makes a system’s behavior harder to predict. Vertical lines = Horizontal lines = queue length at any time wait time in the queue people people People arriving People being served time time ©Alistair Cockburn 2015
Slide 13: Queuing theory shows feed systems run more smoothly with small transfers
13 Queuing theory shows that feed systems like these run more smoothly with small transfers Vertical lines = Horizontal lines = queue length at any time wait time in the queue people people People arriving People being served time time ©Alistair Cockburn 2015
Slide 14: Handing testers 1,000 lines of code or 100 lines
14 This applies when you choose to hand testers 1,000 lines of code to test, or 100 lines of code. Total # of design decisions being validated How long this line of code / screen / use case / decision sits in the testing queue 100 lines of code Testers show up for testing Decisions arriving time Dec
Slide 15: Reduce decisions in motion & balance the flow
15 Reduce decisions in motion & balance the flow Convert jams to continuous flow. UI Designers Users & Testers Sponsors Programmers Business Analysts ©Alistair Cockburn 2015
Slide 16: Design is Knowledge Acquisition
16 Design is Knowledge Acquisition ©Alistair Cockburn 2015
Slide 17: Big-Bang Design is a late-learning strategy
17 Big-Bang Design is a late-learning strategy Growth of knowledge with big-bang integration cost Knowledge comes at the “moment of truth”: final integration. Delivers nearly no knowledge (or risk reduction) time ©Alistair Cockburn 2015
Slide 18: We can pay to learn early in the project
18 We can pay to learn early in the project Growth of knowledge with early, continuous integration Delivers knowledge Development sequence cost indifferent (with respect (risk reduction) to knowledge) time ©Alistair Cockburn 2015
Slide 19: Develop for business value once risks are down
19 Develop for business value once risks are down Knowledge growing Business value growing (risk reduction) cost Reduce risks: - Business - Social - Technical - Cost / Schedule time ©Alistair Cockburn 2015
Slide 20: Three project stages: Risk, Value, Tail
20 Three project stages: Risk, Value, Tail Tail Value Knowledge / risk reduction risk value tail Item1 .. … ... item 2 . … .. item 3 .. … . item 4 .. .. . : time ©Alistair Cockburn 2015
Slide 21: Payoff = Trim-the-Tail: Deliver by value or date
21 Payoff = Trim-the-Tail: Deliver by value or date Trim to deliver Delay to get more on-time (or early) or better ©Alistair Cockburn 2015
Slide 22: Designing in Teams
22 Designing in Teams Craft Professions skills in a medium Cooperative Game communication Flow Management teamwork unvalidated decisions strategies = inventory, lean processes Self-Awareness (Personalities) Knowledge Acquisition the people, strategies, techniques pay-to-learn actually used trim-the-
Slide 23: Postscript: time to deliver a project
23 Postscript: time to deliver a project time = log( D (b..p) ) * N (u..p) * log( N (p) ) time to deliver a project = distance between business owner & programmer (log) * number of people between user & programmer * number of programmers (log) ©Alistair Cockburn 2015
Slide 24: Heart of Agile
24 Heart of Agile Deliver Collaborate Reflect Improve ©Alistair Cockburn 2015