SlideShare a Scribd company logo
1 of 29
Creating a high performing QA function… Simples
By Carl Bruiners
Presumptions
• Continuous Integration (CI) environmental at an embryotic stage
• No Continuous Delivery (CD) model
• No or limited reporting around QA
• Certain aspects around Development / Agile has been omitted to keep the
focus on QA
Note: This should form part of the teams definition of done
Team QA Vision
What is high performing QA
• Testing an integral part of the team
• Automated testing
• Continuous integration / delivery
• Reducing escaping defects
• Eliminating debt
• Reduce uncertainty
• Compliance – Accessibility, W3C, etc…
• Coding standards, practices and patterns
• Improving code base through refactoring
• Features / functions delivered are aligned to commercial requirements
• Hi-visibility of failing tests – i.e. CI / defect information radiators
• Team take shared responsibility for failed tests
• Guaranteed environment up time – Managed through SLA’s
Commercial Benefits
Customer
• Increased frequency of new feature deliveries
• Improved customer experience by reducing likelihood of encountering
a defect
• Improved ability to test granular level functions without impacting on
the product (in combination with A/B or multi-variant testing).
• Improved flexibility to react to competitors
Product
• Reduced time spent on fixing defects = More time spent working on
product features
• Teams work on small incremental feature / function deliveries so that
new features ready for production are not held back by other
unfinished features
• Base product improvement will help extensibility and scalability
• Feature areas are modular, encapsulated independent features which
lessens any escaping defects impacting on other features / areas of
the product
• A/B / Multi-variant testing feedback helps commercial make customer
driven decisions
Financials
• Average daily cost of £58 p/p
• Average effort time per defect 2 days
• Average weekly incoming defect rate 10
Weekly Monthly Annual Target Cost in days
Base £1,160 £4,640 £55,680 n/a 960
1st
Year £696 £2,784 £33,408 40% 576
2nd
Year £11.60 £46.40 £556.80 99% 9.5
Agile Development
Agile Application Lifecycle Management
Agile Delivery Process
• QA integrated within the team
• Refactoring as the team goes along
• Test Driven Development (TDD)
• Pair Programming – to reduce SPOF’s
• GUI / Functional automated testing
• Set a sensible BAU percentage – 20%-30%
• Development practices / patterns – i.e. OO, MVC, patterns, etc..
• Defects reviewed on a daily basis by the PO and team
• Testers validate defects – ensure reproducible steps
• Defining a commercial focused MMFS (Minimal Marketable Feature Set)
• Quality gates in swim lane – Peer review and ready for acceptance (on stage)
Development
Defects
•Testers review incoming defects
•Ensuring defects have enough information supplied
•Identifying priority / severity of defect/s based on commercial value
•Frequently review defects
•Minimise escalations
•PM / PO's to be inclusive of prioritisation of defects
Testing
•Define smoke testing areas on the product
•Adopt Test Driven Development (TDD)
•Introducing Quality Control Gates (QC) into Sprints
Managing Risk
Continuous Integration
Automated testing
•Automated unit testing
•Automated smoke testing
Environment
•Integration server
•SCM – All project deliverables stored under source control i.e. images,
SQL scripts, documentation, etc…
•Builds should happen as frequently as possible
•Continuous visible feedback on testing
•Configuration management
Continuous Delivery – Post CI build
Automated testing
•GUI testing
•Functional testing
•Security testing
•Performance testing
•Regression testing
•Smoke testing
Automated deployment
•Stage
•Production
Continuous delivery workflow
Dev test suite Test suite
Build Performance
Unit test Security
Code scan (U)AT
Compliancy
Regression
GUI
Functional
The Plan
Deliverable goals – Year 1
• Reduce escaping defects through implementing QC gates
• Reduce incoming defects
• Implement / improve CI environment
• Implement CD (inc. fully automated testing)
• Ensure features / functions delivered are aligned to commercial
drivers
• Introduce Quality Controls into Agile process
• Work with teams to ensure correct defects are targeted
• Work with teams on correct best practice development practices
• Measure success rates of defects and improve when needed
• Promote X-team development through sharing each others journeys
• Measure escaping defects
Short Term (Q1 / Q2 2012)
* Note: Subject to change
Medium Term (Q3 / Q4 2012)
Long Term 2013+
My role
• Reshape teams to be more test driven / orientated – Testers embedded in the teams
• Ensure features being delivered on are returning health ROI
• Ensuring commercial alignment;
• Create Scrum of Scrums not only amongst the teams – I attend
• Daily Scrum of Scrums between myself and other Senior Management – Prioritised defect list shared
• Protect the teams from external influences
• Reviewing defect backlogs to ensure that defects being worked on are aligned to commercial alignment
• Stopping enhancements by reviewing the defect backlogs
• Spot review stories to ensure stories are using I.N.V.E.S.T
• Measure escaping defects
• Mitigation of SPOFs
• Ensuring Operations / IT have environments up against a ILSA
• Bring in ISLA’s
• Manage ISLA’s
• Define, manage and negotiate rollback plans
• Define, manage and negotiate dependency reductions – self sufficient teams / department
• Managing other senior managers expectations – transparency / honesty
• Protect teams from external factors that are out of scope
• Manage scope creep
• Resource management – Alignment of staff to peek periods or demands required to meet commercial goals.
• Building strongest equal teams
• Carry out an annual Agile assessment (incorporates QA)
• Organising the introduction of hi-visibility information radiators
• Reduce aged defects over x days old
• CI our QA strategy
• Reduce cost of QA through improved process and productivity improvements
Questions
Handouts
Fig. 1 – Cone of uncertainty
Fig. 2 – Agile test curve
Fig. 3 – CI dashboard
Fig. 4 – Prototyping
Fig. 5 – Scrum Ceremonies

More Related Content

What's hot

Agile Testing Strategy
Agile Testing StrategyAgile Testing Strategy
Agile Testing Strategy
tharindakasun
 
Automation testing strategy, approach & planning
Automation testing  strategy, approach & planningAutomation testing  strategy, approach & planning
Automation testing strategy, approach & planning
SivaprasanthRentala1975
 
How to Design a Successful Test Automation Strategy
How to Design a Successful Test Automation Strategy How to Design a Successful Test Automation Strategy
How to Design a Successful Test Automation Strategy
Impetus Technologies
 

What's hot (20)

Agile Testing Strategy
Agile Testing StrategyAgile Testing Strategy
Agile Testing Strategy
 
Agile modeling
Agile modelingAgile modeling
Agile modeling
 
QA process Presentation
QA process PresentationQA process Presentation
QA process Presentation
 
Introduction to Agile Testing
Introduction to Agile TestingIntroduction to Agile Testing
Introduction to Agile Testing
 
Agile testing principles and practices - Anil Karade
Agile testing principles and practices - Anil KaradeAgile testing principles and practices - Anil Karade
Agile testing principles and practices - Anil Karade
 
Introducing QA Into an Agile Environment
Introducing QA Into an Agile EnvironmentIntroducing QA Into an Agile Environment
Introducing QA Into an Agile Environment
 
Automation testing strategy, approach & planning
Automation testing  strategy, approach & planningAutomation testing  strategy, approach & planning
Automation testing strategy, approach & planning
 
Test automation process
Test automation processTest automation process
Test automation process
 
Agile testing
Agile testingAgile testing
Agile testing
 
Agile Testing - presentation for Agile User Group
Agile Testing - presentation for Agile User GroupAgile Testing - presentation for Agile User Group
Agile Testing - presentation for Agile User Group
 
Agile testing - Testing From Day 1
Agile testing - Testing From Day 1Agile testing - Testing From Day 1
Agile testing - Testing From Day 1
 
Agile QA Process
Agile QA ProcessAgile QA Process
Agile QA Process
 
Agile Testing and Test Automation
Agile Testing and Test AutomationAgile Testing and Test Automation
Agile Testing and Test Automation
 
Testing in Agile Projects
Testing in Agile ProjectsTesting in Agile Projects
Testing in Agile Projects
 
6 Traits of a Successful Test Automation Architecture
6 Traits of a Successful Test Automation Architecture6 Traits of a Successful Test Automation Architecture
6 Traits of a Successful Test Automation Architecture
 
Testing strategy for agile projects updated
Testing strategy for agile projects updatedTesting strategy for agile projects updated
Testing strategy for agile projects updated
 
Scrum Testing Methodology
Scrum Testing MethodologyScrum Testing Methodology
Scrum Testing Methodology
 
Basic Guide to Manual Testing
Basic Guide to Manual TestingBasic Guide to Manual Testing
Basic Guide to Manual Testing
 
Software test life cycle
Software test life cycleSoftware test life cycle
Software test life cycle
 
How to Design a Successful Test Automation Strategy
How to Design a Successful Test Automation Strategy How to Design a Successful Test Automation Strategy
How to Design a Successful Test Automation Strategy
 

Viewers also liked

Agile Testing Process
Agile Testing ProcessAgile Testing Process
Agile Testing Process
Intetics
 
Agile tour ncr test360_degree - agile testing on steroids
Agile tour ncr test360_degree - agile testing on steroidsAgile tour ncr test360_degree - agile testing on steroids
Agile tour ncr test360_degree - agile testing on steroids
Vipul Gupta
 
1 Quality Assurance Presentation
1 Quality Assurance Presentation1 Quality Assurance Presentation
1 Quality Assurance Presentation
guest337c19
 
Quality Assurance and Software Testing
Quality Assurance and Software TestingQuality Assurance and Software Testing
Quality Assurance and Software Testing
pingkapil
 
Software Testing Fundamentals
Software Testing FundamentalsSoftware Testing Fundamentals
Software Testing Fundamentals
Chankey Pathak
 
Overview of Agile Methodology
Overview of Agile MethodologyOverview of Agile Methodology
Overview of Agile Methodology
Haresh Karkar
 

Viewers also liked (20)

Agile Testing Process
Agile Testing ProcessAgile Testing Process
Agile Testing Process
 
Introduction to Agile software testing
Introduction to Agile software testingIntroduction to Agile software testing
Introduction to Agile software testing
 
Agile Testing by Example
Agile Testing by ExampleAgile Testing by Example
Agile Testing by Example
 
Agile tour ncr test360_degree - agile testing on steroids
Agile tour ncr test360_degree - agile testing on steroidsAgile tour ncr test360_degree - agile testing on steroids
Agile tour ncr test360_degree - agile testing on steroids
 
1 Quality Assurance Presentation
1 Quality Assurance Presentation1 Quality Assurance Presentation
1 Quality Assurance Presentation
 
Quality Assurance and Software Testing
Quality Assurance and Software TestingQuality Assurance and Software Testing
Quality Assurance and Software Testing
 
QUALITY ASSURANCE
QUALITY ASSURANCEQUALITY ASSURANCE
QUALITY ASSURANCE
 
Agile Testing
Agile TestingAgile Testing
Agile Testing
 
How to Build in Quality from Day 1 using Lean QA and Agile Testing
How to Build in Quality from Day 1 using Lean QA and Agile TestingHow to Build in Quality from Day 1 using Lean QA and Agile Testing
How to Build in Quality from Day 1 using Lean QA and Agile Testing
 
Test Life Cycle
Test Life CycleTest Life Cycle
Test Life Cycle
 
Test Automation Strategies For Agile
Test Automation Strategies For AgileTest Automation Strategies For Agile
Test Automation Strategies For Agile
 
Testing Best Practices
Testing Best PracticesTesting Best Practices
Testing Best Practices
 
Software testing ppt
Software testing pptSoftware testing ppt
Software testing ppt
 
Test Automation Framework Designs
Test Automation Framework DesignsTest Automation Framework Designs
Test Automation Framework Designs
 
Agile Qa Framework Jacky Wu
Agile Qa Framework Jacky WuAgile Qa Framework Jacky Wu
Agile Qa Framework Jacky Wu
 
What is Agile Testing?
What is Agile Testing?What is Agile Testing?
What is Agile Testing?
 
Testing & Quality Assurance
Testing & Quality AssuranceTesting & Quality Assurance
Testing & Quality Assurance
 
Quality Assurance Vs Quality Control
Quality Assurance Vs Quality ControlQuality Assurance Vs Quality Control
Quality Assurance Vs Quality Control
 
Software Testing Fundamentals
Software Testing FundamentalsSoftware Testing Fundamentals
Software Testing Fundamentals
 
Overview of Agile Methodology
Overview of Agile MethodologyOverview of Agile Methodology
Overview of Agile Methodology
 

Similar to Agile QA presentation

90 days to make a difference - approach
90 days to make a difference - approach90 days to make a difference - approach
90 days to make a difference - approach
Stuart Creasey
 
Deepak R (Process & Test Automation Lead)
Deepak R (Process & Test Automation Lead)Deepak R (Process & Test Automation Lead)
Deepak R (Process & Test Automation Lead)
Deepak R
 

Similar to Agile QA presentation (20)

Software Testing Process, Testing Automation and Software Testing Trends
Software Testing Process, Testing Automation and Software Testing TrendsSoftware Testing Process, Testing Automation and Software Testing Trends
Software Testing Process, Testing Automation and Software Testing Trends
 
Top 10 Business Reasons for ALM
Top 10 Business Reasons for ALMTop 10 Business Reasons for ALM
Top 10 Business Reasons for ALM
 
Top Business Benefits of Application Lifecycle Management (ALM)
Top Business Benefits of Application Lifecycle Management (ALM)Top Business Benefits of Application Lifecycle Management (ALM)
Top Business Benefits of Application Lifecycle Management (ALM)
 
AgileTesting_Ver1.0
AgileTesting_Ver1.0AgileTesting_Ver1.0
AgileTesting_Ver1.0
 
Webinar: "5 semplici passi per migliorare la Quality e i processi di Test".
Webinar: "5 semplici passi per migliorare la Quality e i processi di Test".Webinar: "5 semplici passi per migliorare la Quality e i processi di Test".
Webinar: "5 semplici passi per migliorare la Quality e i processi di Test".
 
Quality assurance and management, software engineering
Quality assurance and management, software engineeringQuality assurance and management, software engineering
Quality assurance and management, software engineering
 
4S Akademi - QAI - Software Testing Principles and Concepts
4S Akademi - QAI - Software Testing Principles and Concepts4S Akademi - QAI - Software Testing Principles and Concepts
4S Akademi - QAI - Software Testing Principles and Concepts
 
7 steps to Software test automation success
7 steps to Software test automation success7 steps to Software test automation success
7 steps to Software test automation success
 
Software Quality Assurance - Software Engineering
Software Quality Assurance - Software EngineeringSoftware Quality Assurance - Software Engineering
Software Quality Assurance - Software Engineering
 
Slow Down to Speed Up - Leveraging Quality to Enable Productivity and Speed w...
Slow Down to Speed Up - Leveraging Quality to Enable Productivity and Speed w...Slow Down to Speed Up - Leveraging Quality to Enable Productivity and Speed w...
Slow Down to Speed Up - Leveraging Quality to Enable Productivity and Speed w...
 
A Comprehensive Step-by-Step Guide for Designing an Agile-Friendly Automation...
A Comprehensive Step-by-Step Guide for Designing an Agile-Friendly Automation...A Comprehensive Step-by-Step Guide for Designing an Agile-Friendly Automation...
A Comprehensive Step-by-Step Guide for Designing an Agile-Friendly Automation...
 
A New Model for Building Business Process Quality
A New Model for Building Business Process QualityA New Model for Building Business Process Quality
A New Model for Building Business Process Quality
 
Total quality management (tqm) final
Total quality management (tqm) finalTotal quality management (tqm) final
Total quality management (tqm) final
 
Setting up Center of Excellence for QA in Healthcare
Setting up Center of Excellence for QA in HealthcareSetting up Center of Excellence for QA in Healthcare
Setting up Center of Excellence for QA in Healthcare
 
Agile testing MyBTEC
Agile testing MyBTECAgile testing MyBTEC
Agile testing MyBTEC
 
90 days to make a difference - approach
90 days to make a difference - approach90 days to make a difference - approach
90 days to make a difference - approach
 
Advanced Product Quality Planning And Control Plans Based On APQP 2 Nd Edition
Advanced Product Quality Planning And Control Plans Based On APQP 2 Nd EditionAdvanced Product Quality Planning And Control Plans Based On APQP 2 Nd Edition
Advanced Product Quality Planning And Control Plans Based On APQP 2 Nd Edition
 
Deepak R (Process & Test Automation Lead)
Deepak R (Process & Test Automation Lead)Deepak R (Process & Test Automation Lead)
Deepak R (Process & Test Automation Lead)
 
Software Testing Process & Trend
Software Testing Process & TrendSoftware Testing Process & Trend
Software Testing Process & Trend
 
CenturyLink's Game-Changing Strategies for Increasing Project Quality
CenturyLink's Game-Changing Strategies for Increasing Project QualityCenturyLink's Game-Changing Strategies for Increasing Project Quality
CenturyLink's Game-Changing Strategies for Increasing Project Quality
 

More from Carl Bruiners (6)

Route to live
Route to liveRoute to live
Route to live
 
Intro to Agile
Intro to AgileIntro to Agile
Intro to Agile
 
Defect management using kanban
Defect management using kanbanDefect management using kanban
Defect management using kanban
 
Agile Edge 2012
Agile Edge 2012Agile Edge 2012
Agile Edge 2012
 
Facilitation
FacilitationFacilitation
Facilitation
 
Agile cambridge 27th September 2012
Agile cambridge 27th September 2012Agile cambridge 27th September 2012
Agile cambridge 27th September 2012
 

Recently uploaded

Breaking Down the Flutterwave Scandal What You Need to Know.pdf
Breaking Down the Flutterwave Scandal What You Need to Know.pdfBreaking Down the Flutterwave Scandal What You Need to Know.pdf
Breaking Down the Flutterwave Scandal What You Need to Know.pdf
UK Journal
 

Recently uploaded (20)

The Metaverse: Are We There Yet?
The  Metaverse:    Are   We  There  Yet?The  Metaverse:    Are   We  There  Yet?
The Metaverse: Are We There Yet?
 
Introduction to FDO and How It works Applications _ Richard at FIDO Alliance.pdf
Introduction to FDO and How It works Applications _ Richard at FIDO Alliance.pdfIntroduction to FDO and How It works Applications _ Richard at FIDO Alliance.pdf
Introduction to FDO and How It works Applications _ Richard at FIDO Alliance.pdf
 
Linux Foundation Edge _ Overview of FDO Software Components _ Randy at Intel.pdf
Linux Foundation Edge _ Overview of FDO Software Components _ Randy at Intel.pdfLinux Foundation Edge _ Overview of FDO Software Components _ Randy at Intel.pdf
Linux Foundation Edge _ Overview of FDO Software Components _ Randy at Intel.pdf
 
Google I/O Extended 2024 Warsaw
Google I/O Extended 2024 WarsawGoogle I/O Extended 2024 Warsaw
Google I/O Extended 2024 Warsaw
 
Free and Effective: Making Flows Publicly Accessible, Yumi Ibrahimzade
Free and Effective: Making Flows Publicly Accessible, Yumi IbrahimzadeFree and Effective: Making Flows Publicly Accessible, Yumi Ibrahimzade
Free and Effective: Making Flows Publicly Accessible, Yumi Ibrahimzade
 
FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...
FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...
FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...
 
Salesforce Adoption – Metrics, Methods, and Motivation, Antone Kom
Salesforce Adoption – Metrics, Methods, and Motivation, Antone KomSalesforce Adoption – Metrics, Methods, and Motivation, Antone Kom
Salesforce Adoption – Metrics, Methods, and Motivation, Antone Kom
 
IESVE for Early Stage Design and Planning
IESVE for Early Stage Design and PlanningIESVE for Early Stage Design and Planning
IESVE for Early Stage Design and Planning
 
Using IESVE for Room Loads Analysis - UK & Ireland
Using IESVE for Room Loads Analysis - UK & IrelandUsing IESVE for Room Loads Analysis - UK & Ireland
Using IESVE for Room Loads Analysis - UK & Ireland
 
Choosing the Right FDO Deployment Model for Your Application _ Geoffrey at In...
Choosing the Right FDO Deployment Model for Your Application _ Geoffrey at In...Choosing the Right FDO Deployment Model for Your Application _ Geoffrey at In...
Choosing the Right FDO Deployment Model for Your Application _ Geoffrey at In...
 
Breaking Down the Flutterwave Scandal What You Need to Know.pdf
Breaking Down the Flutterwave Scandal What You Need to Know.pdfBreaking Down the Flutterwave Scandal What You Need to Know.pdf
Breaking Down the Flutterwave Scandal What You Need to Know.pdf
 
Portal Kombat : extension du réseau de propagande russe
Portal Kombat : extension du réseau de propagande russePortal Kombat : extension du réseau de propagande russe
Portal Kombat : extension du réseau de propagande russe
 
What's New in Teams Calling, Meetings and Devices April 2024
What's New in Teams Calling, Meetings and Devices April 2024What's New in Teams Calling, Meetings and Devices April 2024
What's New in Teams Calling, Meetings and Devices April 2024
 
Overview of Hyperledger Foundation
Overview of Hyperledger FoundationOverview of Hyperledger Foundation
Overview of Hyperledger Foundation
 
Where to Learn More About FDO _ Richard at FIDO Alliance.pdf
Where to Learn More About FDO _ Richard at FIDO Alliance.pdfWhere to Learn More About FDO _ Richard at FIDO Alliance.pdf
Where to Learn More About FDO _ Richard at FIDO Alliance.pdf
 
Speed Wins: From Kafka to APIs in Minutes
Speed Wins: From Kafka to APIs in MinutesSpeed Wins: From Kafka to APIs in Minutes
Speed Wins: From Kafka to APIs in Minutes
 
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdfHow Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
 
Extensible Python: Robustness through Addition - PyCon 2024
Extensible Python: Robustness through Addition - PyCon 2024Extensible Python: Robustness through Addition - PyCon 2024
Extensible Python: Robustness through Addition - PyCon 2024
 
TopCryptoSupers 12thReport OrionX May2024
TopCryptoSupers 12thReport OrionX May2024TopCryptoSupers 12thReport OrionX May2024
TopCryptoSupers 12thReport OrionX May2024
 
Optimizing NoSQL Performance Through Observability
Optimizing NoSQL Performance Through ObservabilityOptimizing NoSQL Performance Through Observability
Optimizing NoSQL Performance Through Observability
 

Agile QA presentation

  • 1. Creating a high performing QA function… Simples By Carl Bruiners
  • 2. Presumptions • Continuous Integration (CI) environmental at an embryotic stage • No Continuous Delivery (CD) model • No or limited reporting around QA • Certain aspects around Development / Agile has been omitted to keep the focus on QA
  • 3. Note: This should form part of the teams definition of done Team QA Vision
  • 4. What is high performing QA • Testing an integral part of the team • Automated testing • Continuous integration / delivery • Reducing escaping defects • Eliminating debt • Reduce uncertainty • Compliance – Accessibility, W3C, etc… • Coding standards, practices and patterns • Improving code base through refactoring • Features / functions delivered are aligned to commercial requirements • Hi-visibility of failing tests – i.e. CI / defect information radiators • Team take shared responsibility for failed tests • Guaranteed environment up time – Managed through SLA’s
  • 6. Customer • Increased frequency of new feature deliveries • Improved customer experience by reducing likelihood of encountering a defect • Improved ability to test granular level functions without impacting on the product (in combination with A/B or multi-variant testing). • Improved flexibility to react to competitors
  • 7. Product • Reduced time spent on fixing defects = More time spent working on product features • Teams work on small incremental feature / function deliveries so that new features ready for production are not held back by other unfinished features • Base product improvement will help extensibility and scalability • Feature areas are modular, encapsulated independent features which lessens any escaping defects impacting on other features / areas of the product • A/B / Multi-variant testing feedback helps commercial make customer driven decisions
  • 8. Financials • Average daily cost of £58 p/p • Average effort time per defect 2 days • Average weekly incoming defect rate 10 Weekly Monthly Annual Target Cost in days Base £1,160 £4,640 £55,680 n/a 960 1st Year £696 £2,784 £33,408 40% 576 2nd Year £11.60 £46.40 £556.80 99% 9.5
  • 12. • QA integrated within the team • Refactoring as the team goes along • Test Driven Development (TDD) • Pair Programming – to reduce SPOF’s • GUI / Functional automated testing • Set a sensible BAU percentage – 20%-30% • Development practices / patterns – i.e. OO, MVC, patterns, etc.. • Defects reviewed on a daily basis by the PO and team • Testers validate defects – ensure reproducible steps • Defining a commercial focused MMFS (Minimal Marketable Feature Set) • Quality gates in swim lane – Peer review and ready for acceptance (on stage) Development
  • 13. Defects •Testers review incoming defects •Ensuring defects have enough information supplied •Identifying priority / severity of defect/s based on commercial value •Frequently review defects •Minimise escalations •PM / PO's to be inclusive of prioritisation of defects Testing •Define smoke testing areas on the product •Adopt Test Driven Development (TDD) •Introducing Quality Control Gates (QC) into Sprints Managing Risk
  • 14. Continuous Integration Automated testing •Automated unit testing •Automated smoke testing Environment •Integration server •SCM – All project deliverables stored under source control i.e. images, SQL scripts, documentation, etc… •Builds should happen as frequently as possible •Continuous visible feedback on testing •Configuration management
  • 15. Continuous Delivery – Post CI build Automated testing •GUI testing •Functional testing •Security testing •Performance testing •Regression testing •Smoke testing Automated deployment •Stage •Production
  • 16. Continuous delivery workflow Dev test suite Test suite Build Performance Unit test Security Code scan (U)AT Compliancy Regression GUI Functional
  • 18. Deliverable goals – Year 1 • Reduce escaping defects through implementing QC gates • Reduce incoming defects • Implement / improve CI environment • Implement CD (inc. fully automated testing) • Ensure features / functions delivered are aligned to commercial drivers • Introduce Quality Controls into Agile process • Work with teams to ensure correct defects are targeted • Work with teams on correct best practice development practices • Measure success rates of defects and improve when needed • Promote X-team development through sharing each others journeys • Measure escaping defects
  • 19. Short Term (Q1 / Q2 2012) * Note: Subject to change
  • 20. Medium Term (Q3 / Q4 2012)
  • 22. My role • Reshape teams to be more test driven / orientated – Testers embedded in the teams • Ensure features being delivered on are returning health ROI • Ensuring commercial alignment; • Create Scrum of Scrums not only amongst the teams – I attend • Daily Scrum of Scrums between myself and other Senior Management – Prioritised defect list shared • Protect the teams from external influences • Reviewing defect backlogs to ensure that defects being worked on are aligned to commercial alignment • Stopping enhancements by reviewing the defect backlogs • Spot review stories to ensure stories are using I.N.V.E.S.T • Measure escaping defects • Mitigation of SPOFs • Ensuring Operations / IT have environments up against a ILSA • Bring in ISLA’s • Manage ISLA’s • Define, manage and negotiate rollback plans • Define, manage and negotiate dependency reductions – self sufficient teams / department • Managing other senior managers expectations – transparency / honesty • Protect teams from external factors that are out of scope • Manage scope creep • Resource management – Alignment of staff to peek periods or demands required to meet commercial goals. • Building strongest equal teams • Carry out an annual Agile assessment (incorporates QA) • Organising the introduction of hi-visibility information radiators • Reduce aged defects over x days old • CI our QA strategy • Reduce cost of QA through improved process and productivity improvements
  • 25. Fig. 1 – Cone of uncertainty
  • 26. Fig. 2 – Agile test curve
  • 27. Fig. 3 – CI dashboard
  • 28. Fig. 4 – Prototyping
  • 29. Fig. 5 – Scrum Ceremonies

Editor's Notes

  1. Work with HR on SM roles – Not having a independent dedicated Scrum Master in the team is like having a football match without a referee, the players know the rules, but we all know that they are unlikely to adhere to them. Back to basics – Some of teams have over complicated their Agile model and lost sight of some of the core values of some of our Scrum ceremonies. This includes all area’s of our model, writing INVEST’ed / SMART User Stories, creating backlog that can be grouped under a release as feature. Improve our training / coaching capabilities – Working with Linda to create a program suite of training development; from the introduction through to advanced Agile. This will include CSM’s, PO training, User Story creation and identifying suitable candidates for training, and also highlighting SPOF removal through training. My view is that all RM’s and SM’s attend the Cohn CSM course and PO’s the CPO course, only after doing the external training then do they sit the GE Agile course (use note about Epic management being incorrect). Improve our CI environments – Get everyone using the same tool Improve our consistency – Create a baseline Agile model and then allow teams to ‘sensibly evolve’, CI will be supported, change for the sake of change won’t be. Understanding a need or identifying a fault will be needed to help justify change Measuring our CI is vital, at present changes are made without any evidence of either need or their success Changing the negative culture concerning Agile – Improve our reporting capabilities – Anyone should be able to generate reports as and when they need without the dependency of another individual. On the fly, real-time reporting.
  2. Decreased delivery cycles – Our delivery cycles are no longer set over years, instead we release incremental value feature releases Deliver meaningful releases aligned to features – Instead of having a fixed release pattern (i.e. every 6 weeks) we shall have variable releases against a features CD including all tests - Our CD environment includes all automated tests, this will also require all manual tests to be replaced by automated testing Fully TDD – Each team becomes test orientated, increasing our QA and reducing the number of escaping defects Improve our consistency using our Tools – Consolidating our tool base, improving integration between tools, etc…
  3. Questions