Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Becoming an Agile Software Architect

You're reading from   Becoming an Agile Software Architect Strategies, practices, and patterns to help architects design continually evolving solutions

Arrow left icon
Product type Paperback
Published in Mar 2021
Publisher Packt
ISBN-13 9781800563841
Length 372 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Rajesh R V Rajesh R V
Author Profile Icon Rajesh R V
Rajesh R V
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Section 1: Understanding Architecture in the Agile World
2. Chapter 1: Looking through the Agile Architect's Lens FREE CHAPTER
3. Chapter 2: Agile Architecture – The Foundation of Agile Delivery 4. Section 2: Transformation of Architect Roles in Agile
5. Chapter 3: Agile Architect – The Linchpin of Success 6. Chapter 4: Agile Enterprise Architect – Connecting Strategy to Code 7. Chapter 5: Agile Solution Architect – Designing Continuously Evolving Systems 8. Section 3: Essential Knowledge to Become a Successful Agile Architect
9. Chapter 6: Delivering Value with New Ways of Working 10. Chapter 7: Technical Agility with Patterns and Techniques 11. Chapter 8: DevOps and Continuous Delivery to Accelerate Flow 12. Chapter 9: Architecting for Quality with Quality Attributes 13. Chapter 10: Lean Documentation through Collaboration 14. Chapter 11: Architect as an Enabler in Lean-Agile Governance 15. Section 4: Personality Traits and Organizational Influence
16. Chapter 12: Architecting Organizational Agility 17. Chapter 13: Culture and Leadership Traits 18. Other Books You May Enjoy

Assessing system quality

Stop-the-line is a technique used in manufacturing introduced by Taiichi Ohno of TPS, where a big red button is pushed whenever someone sees a critical quality issue in the production line. The idea was products with quality issues moved to production have much more severe consequences than stopping the line and fixing problems as and when they occur. Early detection and rectification of defects minimizes wastage. Hence, early and continuous quality assurance is required for the efficient delivery of quality solutions with optimal cost of development.

Brian Marick's Agile testing quadrants are a useful tool to understand various aspects of Agile testing. An adapted version of this was developed by Janet Gregory and Lisa Crispin is shown on the left side of the following figure:

Figure 9.17 – Agile testing quadrants and risk-based performance testing model

As shown in the figure, architecture quality testing is in Q4...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image