Topic: project management

Building a High Performance Agile Team: Assume You Will Be a One Hit Wonder

Michael Walkden, Tuesday, August 25, 2009 @ 9:34 am

One thing about agile teams is that they constantly strive to get better. In my experience an Agile team takes 2-4 iterations to work through the forming stage. By iteration 10 or so the team is past forming and storming and is well into norming. At this stage the team is often moving fast enough or better than expected for the business’ needs. Now the team faces a dilemma: How to become a high performance team and why.

If you don’t keep improving and innovating your competitors will.  However, there is another reason to keep improving that is often missed.  The current success might be temporary or an anomaly.

Don’t fall into the trap of a one hit wonder.

Continue reading »

• Digg
• Reddit
• del.icio.us

Comments (0)

Software Development

Feature Fatigue

Alice Toth, Thursday, June 25, 2009 @ 6:13 am

photo credit: stuartpilbrow

Your project is going along fine. After the initial bumps, the team has reached max velocity and is running through story points like there’s no tomorrow. The demos are a success, with the client loving how everything is coming together. Communication between the team members and the client is working well, with enough give and take that all sides feel like they have a genuine stake in the project. In fact, the goal posts are in sight and we’re already scheduling a release plan. And then the client asks for one more feature. Not a tweak of something already built, but a new feature that has to seamlessly incorporate into the application and not look like a last minute add-on.

The initial response? The team to comes to a screeching halt and devolves into something resembling the stages of grief. Continue reading »

• Digg
• Reddit
• del.icio.us

Comments (2)

software development best practices

The Five Deadly Sins of Software Development

Bernhard Kappe, Monday, April 27, 2009 @ 9:08 pm

There's a list of deadly sins out there for just about anything related to information technology. Some have seven items, some have five, some even have nine. I haven't seen one with 21 deadly sins yet, but I won't be surprised if I do. Some focus on IT departments, some on unused software, some on agile software development, and quite a few on whatever they're trying to sell you.

We've seen a lot in our ten years of developing software at Pathfinder, and the list that rings truest is the shortest and pithiest, from the Standish Group:

• Ambition
• Arrogance
• Ignorance
• Fraudulence
• Abstinence

Each of these is best illustrated by example:
Continue reading »

• Digg
• Reddit
• del.icio.us

Comments (4)

Software Development

Defining RIA Interaction Patterns on time in Flex Agile Development

Sasha Dzeletovic, Friday, October 17, 2008 @ 2:19 am

Putting more attention to User Interaction Design is naturally becoming a standard practice with RIA.

With RIA technologies, classic Interaction Patterns are only building blocks, not solutions. With raised possibilities, Patterns have become more complex.

Continue reading »

• Digg
• Reddit
• del.icio.us

Comments (0)

Software Development