Everand Logo

Welcome to Everand!

  • Discover millions of ebooks, audiobooks, and so much more with a free trial

    Only $11.99/month after trial. Cancel anytime.

    Agile and Quality by Design
    Agile and Quality by Design
    Agile and Quality by Design
    Ebook85 pages1 hour

    Agile and Quality by Design

    By Ronald N. Goulden, MBA, PMP

    ()

    Read preview

    About this ebook

    Agile is not new. Many years ago, project leaders began working closely with the user community and engaged them throughout the entire project process.
    This ensured that the users were involved in determining what they wanted and how it would be presented. Through this natural course of human involvement, the requirements evolved naturally to meet the needs of the customers, ensuring greater satisfaction with the results. By engaging the user, the development team ensured that they delivered to meet the needs of the user and also gained incremental user ‘ownership’ of the product.
    The underlying principle was to place the needs of the customer first. Sometimes, this is referred to as Extreme Programming, or XP. This concept places customer satisfaction first by providing the functions and features the customer wants, rather than what the developer wants to deliver. Typically, this provides a rapid response to dynamic customer demands and encompasses Continuous Integration (CI), which involves frequent changes to the code, and subsequently frequent code delivery.
    Another important function to consider is code refactoring. This involves integrating small changes to the look and feel of the project continuously, over time. Refactoring is not a bug or defect and should not be treated as such. It is merely an aspect of continuous improvement and evolution, and is ideally suited for an Agile environment.
    In 2001, Agile was officially born, though as I have already mentioned, it had actually been in use by many technology departments long before then; it just had not been formalized or named.
    The fact that the Quality Assurance (QA) function is typically compartmentalized away from the development function also aggravates quality issues. Too often, there is an invisible ‘fence’ between the development and quality teams which inhibits teamwork and often promotes an antagonistic relationship between the two groups.
    Isolation of the development and quality teams results in a fragmented effort and sub-standard results. Development rushes to meet a deadline, and quality often has little or no understanding of the user requirements. It is not uncommon for a Quality Assurance team to completely redesign an application after it has been developed and delivered to them for testing.
    This is where Quality by Design can be quite effective by requiring that the development teams are responsible for quality and the quality teams are responsible for understanding the user requirements by being fully engaged in the project from the outset rather than at the end.

    LanguageEnglish
    PublisherRonald N. Goulden, MBA, PMP
    Release dateMay 31, 2015
    ISBN9781311079534
    Agile and Quality by Design
    Author

    Ronald N. Goulden, MBA, PMP

    Ronald Goulden has written novels and stories for thirty years. Having served in Viet Nam as a Translator/Interpreter, He quickly adapts to new cultures and sees a story or an adventure everywhere. He has ‘dabbled’ in witchcraft, though he is not a witch. All of his novels and stories have interconnecting threads that link them into a larger universe, spanning space and time. Some of the links are obvious, while others are very subtle. Some of the events in the stories are based on real life, while others are pure fiction. The distinction between fact and fiction is up to the reader. Having studied witchcraft many years earlier, it had always been in my mind. When I became an IT Director for the Farm Credit bank system in Wichita, I observed the ‘power’ a small group of ladies expressed over others in the bank and their general disdain for many of the men. I had also researched the BTK Killer during his spree and developed a program that allowed me to ‘predict’ his next attacks. As such, I saw the potential for violence in anyone. After being treated rather rudely by the band of bank beauties, I decided to write a story to explain their odd and overbearing personalities. Using newspaper stories and personal experiences, I settled on baby sacrifices and Satanism. While the personalities and physical attributes are based upon real people I knew at the time, their involvement is this story is purely fiction. There are many ‘links’ in this story to the other novels I’ve written over time, essentially building an alternate universe.

    Read more from Ronald N. Goulden, Mba, Pmp

    Related to Agile and Quality by Design

    Related ebooks

    Project Management For You

    View More
    View More

    Related podcast episodes

    Related articles

    • Article

      AGILE: It Is All About Trust

      Oct 22, 2019

      AGILE: It Is All About Trust
      6 min read

    • Article

      Principles of Technical Leadership

      Mar 1, 2022

      IT staff is more than just a number on a spreadsheet. This information is valuable, but it does not tell the whole story. We’ll also need to know about your team’s project history, current (non-hired) CV, and the skills and positions they have—and wa

      2 min read

    • Article

      Refreshed Practice Notes By The DIA For All Designers

      Feb 17, 2023

      Over the years, the Design Institute of Australia’s (DIA) Practice Notes have been a helpful resource allowing designers to gain access to vital professional design information. As part of the recent refresh of all DIA resources planned around the la

      3 min read

    • Article

      Refreshed Practice Notes By The DIA For All Designers

      Feb 17, 2023

      Over the years, the Design Institute of Australia’s (DIA) Practice Notes have been a helpful resource allowing designers to gain access to vital professional design information. As part of the recent refresh of all DIA resources planned around the la

      3 min read

    • Article

      Change Sustainability Your ROI Health Check

      Mar 28, 2019

      Change sustainability programs are as unique as each of the workplace projects themselves. They can be developed either to dovetail into the end of a change program where businessas-usual kicks in, or they can be integrated into a prototype rotation

      5 min read

    • Article

      The Way of The Unicorn: From Start-Up to Scale-Up

      May 1, 2022

      THERE CAN BE NO DOUBT WE LIVE IN INTERESTING TIMES. For those who aren’t familiar with the term, ‘unicorns’ are privately held start-up companies with a value of over $1 billion. And despite the global pandemic, last year we saw more companies reach

      6 min read

    • Article

      The Road Best Travelled

      Feb 25, 2018

      The Road Best Travelled
      3 min read

    • Article

      Customer-centric From Its Core

      Sep 16, 2018

      What’s been the biggest change you have seen in your career? I think one of the biggest things I am seeing recently is data becoming more and more important in how businesses operate and how they deliver customer experiences. Even a few years ago whe

      2 min read

    • Article

      Web App Security

      Jun 29, 2021

      Web App Security
      8 min read

    • Article

      Getting The edge

      Feb 25, 2021

      Getting The edge
      7 min read

    • Article

      Reinventing Jobs

      Mar 18, 2019

      Reinventing Jobs
      6 min read

    Related categories

    Reviews for Agile and Quality by Design

    0 ratings

    0 ratings0 reviews

    What did you think?

    Tap to rate

    Review must be at least 10 words

      Book preview

      Agile and Quality by Design - Ronald N. Goulden, MBA, PMP

      Agile

      &

      Quality by Design

      Copyright © 2015

      Ronald N. Goulden, MBA, PMP

      ALL RIGHTS RESERVED

      Smashwords Edition

      Thank you for downloading this eBook; it remains the copyrighted property of the author, and may not be reproduced, copied and distributed for commercial or non-commercial purposes. If you enjoyed this book, please encourage your friends to download their own copy at Smashwords.com, where they can also discover other works by this author. Thank you for your support.

      Cover design by Ronald Goulden

      Edited by Tamara F. Goulden

      Table of Contents

      Introduction

      Overview – What is Agile

      Agile Mainfesto

      Overview – What is Quality by Design

      Why Combine Agile with Quality by Design

      What is Scrum?

      Scrum Personalities

      Scrum Team Members

      The difference between Scrum & Traditional Project Management

      Scrum Framework

      The Backlog

      Sprints

      Scrum Events

      What Can Go Wrong

      Quality by Design

      Additional Works by Ronald Goulden

      Introduction

      Originally, projects were managed by a process that could be called the Monolithic Project Delivery (MPD) methodology, where the senior IT leadership gathered preliminary requirements from the customer and then sequestered the team until the project was designed and completed. In many cases, an MPD project lasted years.

      Consequently, when the project was finally delivered, it typically did not meet the user’s needs and/or the sponsor lost interest, resulting in costly ‘orphaned’ projects that no one particularly wanted or even understood. Because this methodology captured a static set of requirements in what was very likely an environment of constantly evolving needs, the product was obsolete before it was even delivered.

      Over the years, project delivery methodologies improved to provide milestones and incremental deliverables with associated deadlines. However, regularly slipped milestones resulted in most projects missing the mark on time, money, and quality: under-delivered and over-spent. In fact, quality was often sacrificed in the rush to meet the time or cost delivery requirements; resulting in a sub-standard or completely unusable product.

      In an attempt to solve these problems, the Agile methodology was branded gaining widespread acceptance.

      Many years ago, project leaders began working closely with the user community and engaged them throughout the entire project process.

      This ensured that the users were involved in determining what they wanted and how it would be presented. Through the course of human involvement, the requirements evolved in a smooth and natural, or agile, flow to meet the needs of the customers, ensuring greater satisfaction with the results. By engaging the user throughout the process, the development team ensured delivery of a product that met the needs of the user and also allowed for incremental user ‘ownership’ of the product by the user.

      On the principle of placing the needs of the customer first, the team provides the functions and features the customer wants, rather than what the developer wants to deliver tot eh customer. Because developers provide rapid responses to dynamic customer demands necessitating Continuous Integration (CI), frequent changes to the code, and subsequently frequent code delivery, sometimes this function is referred to as Extreme Programming, or XP.

      A second important function to consider is code refactoring which involves integrating small changes to the look and feel of the project continuously over time. To note, refactoring is not a bug or defect and should not be treated as such. It is merely an aspect of continuous improvement, evolution, and is ideally suited for an Agile environment, as Agile focuses on functionality instead of quality.

      Though it had actually been in use by many technology departments long before, just not formalized and given a name, in 2001, Agile was officially born.

      However, the fact that the Quality Assurance (QA) function is typically compartmentalized away from the development function also aggravates quality issues. Too often, there is an invisible ‘fence’ between the development and quality teams which inhibits teamwork and often promotes an antagonistic relationship between the two groups.

      Isolation of the development and quality teams results in a fragmented effort and sub-standard results. Development rushes to meet a deadline, and quality often has little or no understanding of the user requirements. It is not uncommon for a Quality Assurance team to completely redesign an application after it has been developed and delivered to them for testing.

      This is where Quality by Design can be quite effective by requiring that the development teams are responsible for quality and the quality teams are responsible for understanding the user requirements by being fully engaged in the project from the outset rather than at the end.

      From a business perspective, there is great value to be gained from Agile methodologies. The business can respond more rapidly to the needs of its customers or internal and external demands. However, since Agile focuses on functionality over quality, the developers must take ownership of their efforts, and be responsible for quality through the entire development lifecycle.

      Overview - What is Agile?

      What is Agile? If you go to a browser and search for What is Agile, you will get results that talk

      Enjoying the preview?
      Page 1 of 1