nach oben

2019 | Buch

Kapitel lesen Erstes Kapitel lesen

An Executive’s Guide to Software Quality in an Agile Organization

A Continuous Improvement Journey

verfasst von: Navid Nader-Rezvani

Verlag: Apress

Enthalten in: Springer Professional "Wirtschaft+Technik" , Springer Professional "Technik" , Springer Professional "Wirtschaft"

Einloggen, um Zugang zu erhalten

Über dieses Buch

Utilize a set of practical guidelines to help your Agile organization elevate software design quality as an important business driver to achieve customer satisfaction and, ultimately, higher revenue for your company. This is the first book to focus on a holistic quality view—what it is and how it links to overall business enhancements.

The real-world examples used in this book allow you to learn and apply similar strategies and guidelines to help create a quality blueprint for your organization. Five pillars of quality are defined that can be used for any industry and, once internalized, can serve as a set of tools to continuously improve and measure the key factors impacting quality.

What You’ll Learn

Be aware of the key elements in any transformation that involves culture Link quality and business outcomes Understand quality and its holistic definition and why continuous improvement is still a relevant approach in enhancing quality Follow guidelines with specific examples that can be applied to any product release in any type of industry to improve quality and enhance Agile processes Utilize relevant metrics to measure and continuously improve to make incremental positive changes

Who This Book Is For

Individuals at various levels in organizations—from Agile scrum teams, all the way up to executive leadership

Inhaltsverzeichnis

Frontmatter

Chapter 1. Quality in Agile

How the Two Fit Together

Abstract

I don’t want to sound like Agile is the answer to all our problems in releasing software with high quality. After all, for many years companies had released software, sent human beings to the moon, built aircraft, and achieved many more accomplishments via a waterfall software development lifecycle (SDLC) process. However, with the fast evolution of technology, we have no choice but to adopt Agile and deliver high-quality, incremental value faster.

Navid Nader-Rezvani

Chapter 2. Worldview and Integral Map

Looking at Problems Through Different Lenses

Abstract

Before I walk you through specific examples where quality challenges were addressed by a team and organization, it is important to draw your attention to a concept to which I was introduced by one of my colleagues: Worldview (WV) and Integral Mapping. As a human being, the experiences we have are by-products of our WV—how we see problems and how we deal with them. In this section, I will walk you through the concept and how it is important to talk about these critical and proven factors in your organization before expecting a unified result and DNA-changing actions.

Navid Nader-Rezvani

Chapter 3. Perception of Quality

Holistic Quality Is What Matters

Abstract

Built-in quality is expected and is listed as a table stake in Agile, yet many organizations don’t have a solid quality platform or a roadmap for continuously improving on what is so relevant to customers and their success. When I asked various leaders in an organization what quality meant to them, they immediately responded with “Quality is all about defects.” I had one executive who offered to stop releasing on all product lines and assign every member of the team to close defects that had been comfortably resting in the product backlogs for many years! The executive was basically saying that teams can only work on features or quality initiatives at any given time, not both.

Navid Nader-Rezvani

Chapter 4. Quality Challenges in an Agile Team

Real-World Examples

Abstract

This chapter will include examples of teams that have embarked on quality journeys so as to address various challenges, change their culture, and deliver solutions to customers in a predictable manner. As I mentioned before, Agile processes assume that certain quality disciplines are integrated in the culture of an organization. For example, having a continuous regression automated test suite and an effective build process is assumed. In many organizations, I have witnessed teams struggle with basic value delivery as a result of a lack of quality disciplines.

Navid Nader-Rezvani

Chapter 5. Quality Framework

The Five Pillars of Quality

Abstract

This chapter will focus on how learnings from the individual team experiences were used to create a blueprint and a strong framework for every team across business units to use. Having a solid framework will help elevate the importance of focusing on quality across the board.

Navid Nader-Rezvani

Chapter 6. Assessment Against NQPs (Navid’s Quality Pillars)

Vision, Strategy, Execution, Measurement (VSEM)

Abstract

Now that we have defined the five Navid’s Quality Pillars (NQPs), we need to focus on how to best operationalize them across multiple product teams in both a business unit and an enterprise. Creating a visual radiator to help and remind everyone of the overall quality vision, strategy, execution, and measurements (VSEM) is usually an effective next logical step. The one-page summary in Figure 6-1 can be posted in multiple sites and near high-traffic areas to ensure it generates discussions and ideas start to flow. In one particular organization, we needed the transformation teams to help the rest of the organization adopt and implement these strategies. This visual radiator was a great reminder and reference sheet to which the entire business unit could refer.

Navid Nader-Rezvani

Chapter 7. Agile Quality Test Strategy

Shift Left

Abstract

This chapter will focus on the overall quality test strategy and its importance in an Agile world. Most Agile product development teams develop on cadence and release on demand. An Agile release may consist of multiple program increments (PIs). Being able to fully test new features and ensure there is no regression in existing ones is always challenging. A clear test strategy should be an integral part of every new feature. Ensuring a quality architect (or a very senior quality-passionate technical individual) is included in conversations when a new feature is discussed will be necessary to get the proper level of attention on this very important topic.

Navid Nader-Rezvani

Chapter 8. Quality Excellence Journey

Start with a Proof of Concept

Abstract

At this point, you have seen examples of quality transformations happening within teams and organizations. We have also created a framework for such efforts and discussed the need to start with a Quality Integral Map and create a VSEM (Vision, Strategy, Execution, Measurement) to lead you through your journey.

Navid Nader-Rezvani

Chapter 9. Quality at Scale

Engrave Culture of Quality in an Enterprise

Abstract

Just to add to the complexity, some enterprises may need to adapt to acquisitions and global outsourcing that inevitably raise walls between teams, introduce different tools and processes, and redirect attention to short-term priorities that are not consistent with the business case. To ensure quality has appropriate representation in business discussions, it is important to create a transparent culture, acknowledge challenges with the ever-changing environment, promote standard definitions, and reinforce business metrics that are impacted by product quality.

Navid Nader-Rezvani

Chapter 10. Conclusion and Summary

Abstract

I have covered many examples of how giving “quality” a seat at the table brings fruitful results. The goal was not to write a complete Agile quality playbook, but rather to share enough structured experienced-based examples to allow readers to understand how to create a relevant quality framework for their business. This would also aid them in changing the culture and mindset at all levels and in continuously improving. The examples covered mindset changes that were necessary to engrave quality in the DNA of a product team, a business unit, or an enterprise as a whole. In today’s competitive market, putting customers at the center is no longer an option—it is a given.

Navid Nader-Rezvani

Backmatter

Titel: An Executive’s Guide to Software Quality in an Agile Organization
verfasst von: Navid Nader-Rezvani
Verlag: Apress
Electronic ISBN: 978-1-4842-3751-9
Print ISBN: 978-1-4842-3750-2
DOI: https://doi.org/10.1007/978-1-4842-3751-9