Are You Really Ready To Test Agile?

Diego Lo Giudice

Early this year, on January 15, I published our first research on testing for the Agile and Lean playbook. Connected to that research, my colleague Margo Visitacion and I also published a self-assessment testing toolkit. The toolkit helps app-dev and testing leaders understand how mature their current testing practices and organization are for Agile and Lean development.

The Agile Testing Self-Assessment Toolkit

So what are the necessary elements to assess Agile testing maturity?  Looking to compromise between simplicity and comprehensiveness, we focused on the following:

  • Testing team behavior. Some of the questions we ask here look at collaboration around testing among all roles in the Scrum teams. We also ask about unit testing: Is it a mandatory task for developers? Are all of the repeititive tests that can be run over and over at each regression testing automated?
  • Organization. In our earlier Agile testing research, we noticed a change in the way testing gets organized when Agile is being adopted. So here we look at the role test managers are playing: Are they focusing more on being coaches and change agents to accelerate adoption of the new Agile testing practices? Or are managers still operating in a command-and-control regime? Is the number of manual testers decreasing? Are testing centers of excellence (TCOEs) shifting to become testing practice centers of excellence (TPCOEs)?
Read more

Metadata Investments Are Difficult To Justify To The Business

Henry Peyret

Rob Karel and I (thanks to Rob) recently published the second document in a series on metadata, Best Practices: Establish Your Metadata Plan, after a document about metadata strategy. This document:

  • Broadens the definition of metadata beyond “data on data” to include business rules, process models, application parameters, application rights, and policies.
  • Provides guidance to help evangelize to the business the importance of metadata, not by talking about metadata but by pointing out the value it provides against risks.
  • Recommends demonstrating to IT the transversality of metadata to IT internal siloed systems.
  • Advocates extending data governance to include metadata. The main impact of data governance should be to build the life cycle for metadata, but data governance evangelists reserve little concern for metadata at this point.

 

I will co-author the next document on metadata with Gene Leganza; this document will develop the next practice metadata architecture based partially but not only on a metadata exchange infrastructure. For a lot of people, metadata architecture is a Holy Grail. The upcoming document will demonstrate that metadata architecture will become an important step to ease the trend called “industrialization of IT,” sometimes also called “ERP for IT” or “Lean IT.”

In preparation for this upcoming document, please share with us your own experiences in bringing more attention to metadata.