February 7, 2012

BigVisible Blog

Teams over Projects

Thanks to Derek Huether for bringing up the excellent topic of bringing projects to teams instead of spinning up a new team for every possible need within an organization. Having looked at numerous organizations trying to balance the demands of running too many projects, this is very good advice. However, I think there’s more to this than simply bringing projects to teams. It does not yet answer the root cause of why we try to run too many projects, nor does it answer the key question when that executive responds, “well, Agile’s great, but I would need 5 times my current staff to run all my projects as Agile projects” [Read more...]

Collaborative Play to Solve Problems

Most people within the Agile community seem to be firmly committed to the use of games and interactive exercises for training. I fondly remember first being introduced to the XP Game as a powerful way to demonstrate the values and principles of Agile Software development. While the use of games and play is growing in popularity, I fear that many people hit a roadblock. They frequently see games & play as limited exclusively to the “fun training” domain and don’t appreciate just how powerful it can be for actually solving problems. Indeed, the more I explore this domain, the more I realize that collaborative problem solving is their most valuable use! [Read more...]

Agile and the “Stenographer Analyst”

Thanks to the Boston IIBA for an excellent presentation & discussion last night about collaboration, requirements and how the role of the analyst fits into an Agile project. For me, the discussion was quite interesting and I came out with a couple key points that are worth reiterating. I find myself being confronted with the question, “so what does an analyst do in an Agile project?”. There are a number of derivations on this query, but the thinking seems to go something like this: the job of the analyst is to write the requirements, if we’re now putting the customer in direct contact with the development team, what’s the point of an analyst? One participant even mentioned that taking a complex document away and simply helping people write user stories sounded like “a glorified secretary”.

[Read more...]

Sending your code to the Car Wash

I really like hanging out with Test folks. Their clarity and willingness to face what is happening is refreshing, invigorating and also a complete downer.
Sunday at Agile 2010 was the aa-ftt workshop and some of the most important thought leaders you don’t know were going at hammer and tong.
A couple of hours into “Al” (an Alias because I can’t get a hold of him to ask permission to quote) said “Developers treat test as the car wash, they drive their code up and expect us to clean off the bugs on the windscreen”. My mind went into hyper drive and the great comedy “Car Wash” would not leave me alone.

“Al” was right on the money.  In a traditional or even many agile-lite environments stories are planned, tasks created and – at the very end of the sprint (if you are lucky) the test task is there.  Yup.  Here comes the latest in cool code.

It is like you build a car got it ready to roll and took it to the car wash.  When it comes out the other end you are really upset because it is full of water, soap, and all the pizza bones, old soda bottles, and that missing fooz ball are floating around in the  passenger compartment.  Jeez those clowns at the car wash should have been more careful.  Didn’t they see the windows were mocks, the roof was a shell, I mean all that was need was to clean the three little bugs off the windscreen and fine tune the horn.

In a more mature agile shop there would have been an acceptance requirement that the code had to be able to go through the car wash.  But even that level of sophistication will fail because it lacks the clarity of why it has to go through and most of all what it should look like after it is done.  three fourths of this car came out the other end, the wheels, rims, and interior were lost, and the team was incensed they could get the credit for the work that past. – all because the clowns at the car wash won’t take a broader view of the acceptance criteria – I mean come on dude, Most of it got through.

Then there is the business attitude toward the car wash employees.  The dudes with the rags get labeled surly, arrogant, and picky as the dickens when it comes to NOT doing somethings.  Business wants a good job for as little as they can pay for.  Look is it too much to ask for a clean car, vacuumed mats, windows that shine, as well as the removal of the unknown projectiles lodged in the mini-grill of the sub woofers stored in the trunk?  No I am not going to pay all that money for a detailing job so the car looks as good as new.  I just want to have it look that way for no additional cost.  And while you are at it, balance the engine, tune the suspension, lube it and put in the best oil and filter you can.

So thanks big Al.  We are all going to start moving to the tune.

Taking Agile Beyond “Faster”

In November, I spoke at several Agile Journal events in the Northeast about the benefits of using Agile and how they transcend simply “going faster”. I have already posted the presentation, but like most power point slides, it does not stand that well on its own, so I wanted to write up a summary of my thoughts on this topic for the ages, as well as to develop my own thinking. I share these thoughts with you now. [Read more...]

Iteration Tracker

I’ve been asked recently to post the Standalone Iteration Tracking Spreadsheet that I created a few years back – and I finally got around to it.  This spreadsheet was first part of a bigger tool that supported backlog management, release reporting, feature tracking etc.  It became incredibly difficult to maintain so I decided to pull key pieces out and made them independent.  This Iteration or Sprint Tracker is intended to be used by ScrumMasters or Project Managers.  It was never intended to be used by the entire team (though you absolutely can) but rather provide a way for the ScrumMaster to actively track task progress and generate real-time reports and diagnostics.  You will see that it provides far more than the simple traditional burndown.  Along with the Advanced Burn-up it also shows the Category Burn-down.  The Category Burndown is intended to show visibility into the progress of specific categories of task – to identify bottlenecks or constraints. [Read more...]

Might as well admit it, you’re addicted to story points

One of my favorite teachers in college was a former managerial consultant and our class enjoyed being regaled with stories of her former clients – a veritable who’s who of major companies – and the challenges they faced. I recall one lecture when she was telling us about reports and communications and how you need to understand the psychological impact they may have on an organization. She was working with a major department store in the early 90′s when the organization was in a steep decline. [Read more...]