Pivoting Your Organization to Become Agile Testers
Many organizations struggle with transforming from the old style teams consisting of members with specialized silos of skills into Agile teams consisting of generalized specialists. This results in sub-optimal Agile adoptions in Agile/Scrum environments, which is where most organizations transforming to Agile are advised to start.
We will start with a look into the real role of QA in the organization, and where they truly add value in the production of quality code to allow the business to move forward. Piggybacking on the role of QA, we will then speak to exactly what QA needs to do to add value to the software development process, and how they integrate in the DevOps model that is a contemporary solution to an age old issue. And, finally, we will speak to some uncomfortable truths, and draw conclusions into the skills that Agile Testers must be expected to master to allow the organization to pivot successfully into a truly Agile development group.
Outline/Structure of the Talk
This talk has been given at STP 2013 (San Diego CA) and will also be presented at Agile Development and Better Software East 2013 (Boston MA, in the fall). I will substantially use the same material, but will have cull it down and tighten it up a bit to fit within 45 minutes.
- For Agile and Scrum to work, QC in the organization must become QA, and integrated with the rest of Delivery
- Lean thinking has direct applicability in terms of reducing waste due to large batch sizes that results from traditional QC testing
- Lean thinking has direct applicability in terms of avoiding the evils of both Scrummerfall and matrixed organizations
- There may be up-skilling for QA to operate effectively in the new arrangement, but that’s good for everyone
QA, Developers, Managers
schedule Submitted 6 years ago
People who liked this proposal, also liked:
Doc Norton - Creating a Global Engineering CultureDoc NortonDirector of EngineeringGroupon
schedule 5 years agoSold Out!
Creating a Global Engineering Culture
Howard Deiner - Contracts in the Age of AgilityHoward DeinerAgile Process and Technical Practices CoachSolutionsIQ
schedule 6 years agoSold Out!
“Fixed price, fixed deliverables, and fixed schedule” contracts are just about the worst way to write contracts involving software, yet they are the most popular – so what are some techniques to use to fix that?
Organizations that perform professional services for software development or develop software on a work for hire basis are usually engaged bound by extensive contracts. These contracts are typically characterized as “fixed price, fixed deliverables, and fixed schedule.” These, of course, are the vertices of the “Iron Triangle of Software Development” and foreshadow a poor outcome due to issues that make the requirements gathering and project estimation phases that precede contract negotiation so prone to error.
Given this, the question becomes one of “how can I engage clients in a way that allows us each to achieve our goals?” If Agile and Lean methods are the status quo for good development practices, how can I write contracts for development services that embrace this mindset and let each side achieve it’s goals better? This lecture and roundtable explores the many facets of this question and provides the attendee answers that they can use going forward.
Howard Deiner - The Agile PMO - Creating A Lean Organization from the Inside-OutHoward DeinerAgile Process and Technical Practices CoachSolutionsIQ
schedule 6 years agoSold Out!
For many, the idea that you can transform an organization from the PMO outwards seems odd, if not impossible. But my experience says that this is becoming a trend that more and more clients are asking advice for.
We know that for an Agile transformation to work, we need to engage not just the Delivery Teams to approach work differently, but we need a change agent high in the organization to support that change in mindset. I’ve always found it difficult to find that right person in an executive leadership role who is willing to have the courage to “bet the company” on a new and unproven approach such as Agile and Scrum. As coaches, we tend to start “pilot” projects, and hope that traction will occur “once everyone sees the great results that we get.” But I think that this approach is fraught with peril of not getting the right project to start with, not getting the right results immediately, and not motivating people by seeing results from a process that they are not comfortable with.
I think I’ve come upon a new approach that works better. Instead of trying to “sell” Agile at an Enterprise level, embrace pure Lean principles high in the organization and work with the PMO leader at the organization. Once they are comfortable with ideas such as “more leadership and less management”, “shorter concept to cash cycles”, “enabling Lean Startup mentality for disruptive product development”, “always looking for the elimination of waste”, “exploiting variability through appropriate cadence control and appropriate utilization rates”, “delegated authority”, “continuous improvement”, and “rolling planning”, the PMO becomes a terrific agent for instituting change, because they are usually already endowed with the right responsibilities and accountabilities that can push the organization forward.