Agile On The Beach 2015 Quality Paul Massey Founder and Director Bluefruit Software
Agile On The Beach 2015 • Bluefruit established in 2000 • Embedded Software Specialists • Clients in Automotive, Aerospace, Scientific Instruments, Consumer Goods etc. • Strong Quality focus • Agile since 2009 • Influenced by Lean-Agile
Agile On The Beach 2015 • What quality means to us • Why we believe it is important • How we have navigated the journey so far
What Quality means to us
What Quality means to us Exactly what I was Never goes Great build It just looking for wrong quality WORKS! You almost Simple, yet forget its effective Upgrades Really adds there! Stunning to are to the look at seamless experience Completely It has saved intuitive Feels like Never us a fortune part of your ceases to A real body Makes the impress me timesaver job so much Works first easier Really helps time, every I wish I had Well to complete time thought of architected the task it!
What Quality means to us Exactly what I was Never goes Great build It just looking for wrong quality WORKS! You almost Simple, yet forget its effective Upgrades Really adds there! Stunning to are to the look at seamless experience Completely It has saved intuitive Feels like Never us a fortune part of your ceases to A real body Makes the impress me timesaver job so much Works first easier Really helps time, every I wish I had Well to complete time thought of architected the task it!
What Quality means to us How it “feels” What it delivers How it is built
What Quality means to us User Experience We believe these two concepts are what makes up We call what the user experiences and define the true meaning ‘Perceived Integrity ’*. of quality in software. How it is built The way it is built is called *Mary Poppendeick’s ‘Lean Software ‘Conceptual Integrity ’*. Development : An Agile Toolkit’
What - Perceived Integrity Pleasurable Meaningful User Experience Usable Economical Reliable How it is Functional built
What - Conceptual Integrity Conceptual Integrity includes the elements that are going on beneath the User User Experience, but also include things that the Experience end user will never see or engage with. Habitability How it is Scalability Maintainability built
What – Cultivating Quality
Why is Quality Important? • Our vision: • Happy Customers • Happy Workforce • Successful Projects • Quality is not just for free… • … it pays
Why – Quality Pays Quality is a Strategy, NOT a tactic…..
Why – Successful Projects Traditional “Iron Triangle” Fixed Scope Cost Time Variable Quality is the hidden variable in the “iron triangle”. It is often the first to be compromised, followed by deadlines and then budget.
Why – Successful Projects Traditional “Iron Triangle” Fixed Scope Cost Time Variable Quality is the hidden variable in the “iron triangle”. It is often the first to be compromised, followed by deadlines and then budget.
Why – Successful Projects Traditional Agile Fixed Variable By placing Quality First and constantly prioritising scope (alongside budget and deadlines), we deliver the best probability of project success.
Why is Quality Important? • Quality is a strategy, not a tactic • Quality Pays • Quality First delivers: • Successful Projects • Happy Customers • Happy Workforce
How is Quality achieved? • There are three key constituents in the creation of Quality Customer • The Customer • The Engineering team • The product itself Engineer • We use the Agile Toolkit to create feedback loops Product
How is Quality achieved? • There are three key constituents in the creation of Quality Customer • The Customer • The Engineering team • The product itself Engineer Product
How - The Quality Wheel • User The effectiveness of the Experience interaction between these constituents is key to the successful outcome of a Quality Solution Customer Product Programming Requirements Perceived Integrity Engineer Conceptual Integrity
How - The Quality Wheel User • But what about bugs?!! Reported Bugs • The software doesn’t do what the Customer expects it to do • Sometimes this is because the Customer Product Engineer has made a mistake in the coding • Often, in our experience, it is Requirements Coding because the requirements Bugs Bugs don’t accurately describe what the Customer expects Perceived Integrity Engineer Conceptual Integrity
How - The Quality Wheel • How Agile Helps Quality UX • Goal: A Quality User Experience • Build the Right Thing - BDD Customer Product • Build the Thing Right - TDD Test Behaviour Driven Driven Devt. Devt. Perceived Integrity Engineer Conceptual Integrity
How - TDD and BDD BDD TDD Make test pass Automated Write Acceptance “ f ailing” Test test Acceptance Criteria Refactor Customer
How - The Quality Wheel • Goal: A Quality User Quality UX Experience • Build the Right Thing - BDD • Build the Thing Right - TDD Customer Product Test Behaviour Driven Driven Devt. Devt. Perceived Integrity Engineer Conceptual Integrity
Bringing it all together What Why How
Recommend
More recommend
