TPS reports, courtesy of the movie Office Space, have become nearly a cultural in-joke about useless paperwork for those of us who work in office environments. I recently saw an article that described the A3 technique, which is far from useless. The technique comes from the book Managing to Learn: Using the A3 Management Process by John Shook.
What I really like about this technique is that it seeks to concentrate all the necessary information down into a single piece of paper, albeit a large piece of paper. While the details of issues we face on a daily basis are often extremely complex, the level of detail needed to make an informed decision rarely needs that same complexity. Space is limited, especially if the information is going to be legible, so brevity is a must. Nothing beyond what is necessary is contained within the document.
I also love that this is meant to be ad-hoc. No time is wasted trying to format and 'pretty up' a document that is meant to be used. For those of us who are spelling-challenged and depend upon our word processor's spell-check functions, creating our A3 by hand is especially challenging, but it also forces us to not be so reliant upon technology.
The last thing I really enjoy about this is how visual it is. I've noticed that certain groups of stakeholders, especially those that are not in finance, generally respond better to graphical representations of processes than they do to a large list of textual requirements. This presents the information stakeholders need in a format that works well for most of them.
What about you? Could you use A3 in your projects?
Subscribe to:
Post Comments (Atom)
Popular Posts
-
Due to popular demand I have aggregated some information on User Stories and created a simple template. If you feel this would be useful to...
-
I have been having a bit of a discussion over at the IIBA blog with Kevin (VP BOK) and Julian (Chief architect.) It’s migrated over to ...
-
Better Projects Templates I am uploading a couple of project document templates to Google Docs. As I add more I'll post them up here. You...
-
You've heard many reasons why project fail. Here is a discussion hosted by BCS on why projects work. The discussion covers four dimensio...
-
The Precedence Diagramming Method ( PDM ) was developed in the early 1960s by H.B. Zachry in cooperation with IBM. It has largely repla...
-
In the below video some of the #10yrsagile participants discuss the role of the Business Analyst. A question for you; Do you agree or di...
-
This is a guest post by Jeff Hobbs. Jeff is a project manager at ActiveState Software who provide pm and collaboration software. Email, ...
-
In one of the Carnivals of Business Analysts the theme was “ Requirements Analysis ." I searched the web far and wide and came up with a n...
-
I'm a massive Lord of the Rings fan. Every year, I spend part of my holiday vacation rewatching the 12 hours of the blu-ray extended edit...
-
The definition of a stakeholder is controversial. For example, project team members are generally not considered stakeholders, but in virtua...
Absolutely agree. I was about to write a blog called 'Restrict yourself' on situations when it is counterproductive for a BA to be thorough.
ReplyDeleteIt's been my experience that there are phases when you want to have the essentials. If you allow participants to throw in everything plus the kitchen sink you will lose the ability to determine what is really important because the 'everything is important' mindset kicks in all too easily
I had not heard of the A3 technique before, but I can immediately see the value. So many times there is way too much (unneeded or duplicate) information. Cut right to the heart of the problem and how to solve it.
ReplyDelete