The anti-patterns for an agile organization

On November 5 there will be the 2nd Agile Leadership Day here in Zurich which will be another excellent chance for senior management and others to learn about the agile movement and the benefits that agile brings. I recently came across an organization who had declared „Mission accomplished“ for becoming agile. I found – let’s say – a few anti-patterns why that was far from the case.

The slaves in a Scrum team

To make a project successful, it needs someone providing the vision, goals, and leadership, a role overseeing the constraints like tasks, budget, and time, as well as someone ensuring the efficient and effective use of resources in order to produce the desired quality. These roles need titles. Using the right or wrong words can have a great effect on people. There are lots of words that intrigue me why people are using them and whether they understand what they actually mean.

The HP in requirements management

Every role in an organization has the tendency to see his/her task as a silo: e.g. we deliver requirements in an un-manageable Microsoft Office document and let the readers decide what they want to do with our requirements. Some organization begin to use integrated tools like HP's tool suite. Although not the best tool for requirements engineering, HP provides an excellent tool to manage requirements, test cases, and the traces among them. When deciding whether the HP QC licenses are enough or HP ALM should be used, there are certain features of HP ALM that are a must.