Bits & Chips published the first part of my new article on agile transformations. Analysing the various organizations I’ve worked with, I distinguish three separate waves, each with its own challenges and scope. Understand the three waves of agile enables us to have a better grip on Agile transformations and helps agile coaches to explain why they focus on certain aspects. It puts our interventions in perspective and provides a roadmap for the organisation. But last but not least I trust the article will provide insight into how the role of Agile coaching is developing.
Part one of the article describes the first two waves. In two weeks time we’ll publish part 2 that will describe the 3rd wave and contains a table that summarises the challenges for each wave.
The 4th edition of Agile Amsterdam will be held in September 2020. The conference aims to nourish and cultivate the agile mindset. The conference program consists out of a warming-up evening, a full day of talks, workshops and open space sessions that are followed by masterclasses on the second day.
Although the event seems still far away in time the first speakers are announced. Confirmed companies and speakers to date are Mary Poppendieck, Dave West (CEO Scrum.org), Bloomberg, Booking-com, Shell (tbc), and more
I recently obtained myself a copy of Leading Quality by Ronald Cummings-John and Owais Peer. The black book cover contains five stars and a subtitle: “How great leaders deliver High Quality software and Accelerate Growth”. Being extremely interested in agile leadership and built-in Quality, I was sold. I read the book and believe it was a wise decision to but the five-star rating already on the cover. I thought it a valuable read.
Although the book is a book for testers, the book does not
explain how you can do your tests. As Neil Brown states in the foreword. Being just
good at testing is no longer sufficient. Quality is key to business success and
test-leads must impact teams throughout the organization, align with business
teams and work within the overall goals and directions of the business. The
authors introduce the quality narrative, you can talk about the responsibility or
ownership of quality, the right way to test or focus on the value of testing. In
the following chapters they discuss topics that help to build a quality strategy
and shape testing so it adds value.
For example, the discussion on Continues Testing helps to understand
why you do certain tests. It is more than automating tests. Ronald and Owais rather
define continues testing as the ability to test an application in every stage
of its development cycle. The table by Elisabeth Hendrickson (page 66) links
test questions with types of tests and invite you to think about testing on a
more strategic level. What do you want to learn from your tests?
I liked the approach explained in chapter 5. The authors
explain how a new product evolves and the testing purpose shifts accordingly. A
clear example is given of a game manufactory that initially doesn’t care that
much for quality, but rather validates whether the product is the right product.
Predictability and scaling are relevant but later product life cycle.
Conclusion: the quality strategy follows the product life cycle.
In the rest of the book automation, infrastructure, Growth Metrics and Persona’s are discussed. In the last chapter all previous topics are combined into one quality strategy. Great leaders start with a clear vision, but you need not only to know where you are going, but also where you currently are. The example of Ashley that mapped the development pipeline and overlaid the testing process on top of it, is one more inspiring example and I believe in the value of this practice. The rest of the chapter refers to the preceding chapters that form the ingredients of the quality strategy. A good quality strategy is one step towards built-in quality, so I am pleased that now there is a book on this topic available. Personally, I think the last chapter could have been a little more elaborated, but for me, the book earned all five stars that are already printed on the cover.
I am excited to announce that I will be keynote speaker at Tesena Fest Vienna on March 5th 2020. I’ll be talking about Built-in Quality, a topic that I am really enthusiastic about. I believe it is a topic that rightfully is gaining more attention. Although Built-in Quality is a core principle in Lean and the Scaling Agile Framework, for many it is not clear how you build quality in. I have been publishing and talking about embedding Quality in SAFe (see e.g. ebook Q in SAFe) and BIQ is part of our Test managent workshop. But think there is more to tell. I am looking forward to bringing my insights together in one inspiring keynote.
This week Jan Jaap Cannegieter and I had the honour to present a keynote at the Agile Testing Days in Potsdam. In our keynote “The challenges ahead we discussed trends that we see around us and how these challenge us. One conclusion is that we are more likely to be confronted with new technologies and applications of these technologies and we are more likely to be in a situation where we do not know how to test it. So adoption new skills and knowledge and learning are crucial. During the keynote we also looked at this years conference program, to highlight sessions that relate to the challengers that lay ahead….
The last year I became aware of a growing ‘flying shame’. Did you hear other people apologize that they take a flight or maybe you yourself searched for alternatives that are more environmentally friendly….
I used this setting for a new case: “The green traveler.” I will use this case as basis for my workshop at the EuroSTAR conference this year. In the “Planning and Testing your releases” workshop we will prioritise our backlog, define valuable releases and make a roadmap. See more details on the conference website.
The Testing Retreat is an international peer conference that aims to discuss relevant test topics and inspire its participants. During this 24th edition we had 13 participants from the Netherlands, UK, Belgium, Poland, Denmark and even the USA. During normal conferences there is mostly little time to have the in-dept sessions of the kind that the retreat hosts. This weekend we gathered in Friesland to discuss:
The role of the tester in Agile development
Scaling agile and the the place of the test manager
Feedback driven testing
DevOps and Testing
Test automation research
Metamorphic testing in non determinant systems
Updating the 2012 Mapa Testi
During the breaks dinner and time-of moments we discussed a lot of different topics as well. It was a very nice, inspiring weekend, that I trust enables participant to improve their value as test professional and to see developments in right perspective. I am already looking forward for next year’s edition, which will be the 25th edition.
This week I started with Squerist. The last 9+ years I have worked at Valori and did many beautiful, interesting and fun things. Things that stand out among these are embedding the quality into development, setting up test strategies and helping organizations with their agile transformation. I will continue to do so within Squerist. Squerist is a Dutch consultancy company that is specialised in progression. Their mission is to continuously improve and develop their employees, their customers and their expertise. They already offer services on Software testing, Business transformation and Security. Together with Squerist I’m going to see how we further grow our agile services and make it into a fourth group of services. A great opportunity that I love to embrace! I believe my passion for quality and agile practices fits right in.
Choosing something also means saying no to something else. Unfortunately, I have to say goodbye to Valori. But I hope to meet you all in my new context, as Test Manager, Agile Coach or at one of the conferences to which I contribute.
With Valori we published a new eBook in the series on Digital transformation.
This publication is a follow up on the trend report that was released earlier this year. In this previous ebook we described disruptive trends and explained why organisations need to become adaptive. In this second edition we focus on the development practises that companies embrace to do so. In the first part we describe how Agile, DevOps, CI/CD and Scaling contribute to business agility. I believe it is a nice introduction for managers, stakeholders and professionals that are not entirely familiar with these development practises.
The second part of the eBook deals with Built in Quality. We state that the concept of creating fast feedback loops crumbles when you cannot release frequently. Without confidence in system quality, we cannot make quick adjustments and receive no feedback on the impact of implemented improvements. Built in Quality provides the confidence in the quality of the systems so that we dare to change them frequently and take them into production. In the eBook we introduce the built in quality circle. It provides an overview of the steps in the development cycle and where errors can be prevented.
I stumbled on an interesting webinar by 321Gang.com on how to incorporate testing on the various levels in the SAFe framework. Wade Towles explains that Built-In quality is one of the Scaled Agile Framework’s (SAFe) four Core Values and a core principle of the Lean-Agile Mindset. In the webinar he explains how to Incorporate Testing in a SAFe Development Process using Rational Quality Manger (RQM). Keeping track of what needs to be tested and how is critical for success, especially in regulated environments.
The webinar describes the relationship between requirements on epic, feature and story level (at approx 7:15 min) and shows how capability, feature plans and system demo plans are required to organise testing.
Wade states (at approx 8:30 min) that in order to have effective testing at team level the system team 0r the integration test team should write a PI testplan for the program with a child testplan for each feature in the PI. This Feature testplan ties together the tests done on each features
Likewise at System demo testplan is used at solution level (at approx 16:20 min). This plan can be made by a team of e.e. solution architects, Business architect of test engineers and looks for successful completion at a solution level The focus of the System demo testplan is to test how the features work together rather than testing the individual features.
What I notice is that the testplan seems to be a collection of tests rather than a testplan that describes how the tests are organised. For me a testplan is often the later. I guess we need both. I mis a mention on what should be a testplan to effectively align different parties and teams to collaborate on integration testing. But beside this omission, it is an interesting webinar, and I am glad more people start talking about embedding quality in scaled agile settings.
Yesterday we had another of our Quality in SAFe meetings. The Special Interest Group is founded by TestNet and aims to define where quality and testing can be mounted into scaled agile organisations. Yesterday we had an interesting discussion on responsibilities. Where should we put the quality responsibility on team and release train level and how does this answer differ when moving from an informal to a highly regulated organisation. We discussed the roles of the productmanager and the RTE with respect to test management and QA. We talked about the function of the systems team and the CoE in providing guidelines and support.
If you are interested in joining these discussion. We meet regularly in regio Utrecht and love to hear your experience and ideas as well. Contact TestNet or Me (Derk-Jan).
About the theme: Many organisations struggle with transforming into a flexible organisation. Some organisations have completely or partially reversed their Agile transformation and ask: Does the transformation to an agile organisation actually have the intended effects? The answer to this question can be confronting …On the other hand, we know of organisations where the transformation to an agile organisation is a success. Organizations where motivated employees and teams deliver the right value to a satisfied customer every day. How have these organisations succeeded? How do you unlock the power of Agile? This is the central question this year that the Agile Consortium’s annual congress wants to answer.
It promises to be a day full of interesting presentation and workshops. Mark 10 October in your calendar, and check the program. As the program is being made the website is updated in short iterations. Check out the preliminary program on the conference website.
During a full day we discussed the needs for agile test strategies and what role the test manager can take. During the day we collected and prioritized the activities that test managers do and compared them the needs of the stakeholders.
During our hands-on exercises the participants worked in small groups on single-team one-page test plans. We learned how to incorporate non-functional tests and how present the strategy in a visual way using a simple graphic of mind-map. Since we did this tutorial in Copenhagen last month, the quality in a scaled agile setting has become a valued topic on the agenda. So, we discussed how quality can be embedded in a multiple team setting.
In the last hour of the day, we looked at different roles that a test manager can take. We examined the benefits and activities for each role and shared our insights.
We were very pleased with the enthusiastic participation and the high level of discussions we had. We loved the feedback we got on the feedback form (nines and tens) and during the rest of the conference. Many come towards us to share how they valued the session.
See below an impression of the day:
If you are interested in our tutorial, feel free to contact me, of visit the Agile Testing Days in Potsdam later this year. We will host the training there as well.
The annual state of testing report is based on the contribution of about 1000 participants from 80 countries. They filled in the survey earlier this year and thus sharing how they perceived their work and the testing profession.
PractiTest and TeaTimeWithTesters are happy to present the report. It’s the 6th edition already. It brings you a lot of data and numbers, and also clarifies trends that are relevant to everyone seeking a future in the QA world.
Have a look at page 13, and see how CI/CD is getting more adopted.
See how the number of testers that don’t do automation goes down,
or look for the team challenges on page 25.
Check how people expect their career to evolve on page 31
Just a few of the highlights, Download it now and discover: