The Latest

Tips and Advice - The three basic things - Simple but not easy

Test plans are seldom followed as written, project plans hardly ever fit the actual progress, and process models are rarely followed to the letter. Markus Gaertner examines why most of our documents become obsolete and gives advice about whether or not to continue to write and maintain them.
 

Every action elicits a response, but sometimes that response is not what we expect. These anecdotes from industry experts are good examples of how our best intentions don't always match our plans.

Mistakes happen. It's how you respond to them that matters. Teams might react to a bug with panic and blame, leading to a quickly hacked fix and possibly more issues. Taking time to investigate and learn leverages problems into process and practice improvement and a higher quality product.

Here is what Mark Lines (Unified Process Mentors, Co-Founder) has to say:

The fact that basic agile concepts are so easy to learn, as well as the proliferation of certification courses with very little investment required has had both positive and negative effects. Certainly the mindshare of methods such as Scrum has exploded in our industry and people are excited about the benefits that agile can deliver in terms of elimination of waste and timely delivery of systems with immediate ROI.

Agile embraces the concept of self-organizing teams but they are inherently unstable and are only successful when the ‘Leadership – Self-Management’ dilemma is understood and dealt with. Too much central control destroys agility, inhibits creativity and resists change. Too much self-management leads to chaos and anarchy and destroys a team. A successful Agile Team needs to operate as far along the continuum towards self-management as it can, without tipping over into chaos. You can’t just eliminate the PM role and say to a software development team, “OK, you’re now an Agile Team – you need to self-organize”. This is a recipe for failure, and one of the reasons why many organizations resist the Agile approach.

Complaints in the workplace about insufficient or inadequate communication are common, yet that very word "communication" is subject to multiple interpretations.

Here's an example of what I mean: A director had a survey conducted to determine the cause of his employees' low morale. One of the key findings was their desire for more communication. Eager to put things right, the director began circulating more reports and email than ever. And as a voracious reader, he started to extract articles from his many periodicals and circulate them to everyone.