Planbox Tips: 4 Elements for an Efficient Iteration Planning Meeting

Tuesday, September 25th, 2012

There are generally 3 levels of planning that occur in agile project management practices. First, the Project Roadmap outlines high-level components that you wish to accomplish. Then, iterations help you break the whole project into manageable chunks, allowing you to build your project iteratively as you move forward. Finally, in the stand up, your team plans tasks for the day, discuss together what will be accomplished during the day and the potential obstacles you will face.


Following last week’s Planbox Tips on benefits of doing iteration reviews, this week, we stay at the level of iteration planning, and  discuss about 4 key elements that will help you run an iteration planning meeting efficiently.

 

1. A Groomed Project backlog
A disorganized project backlog can quickly become the land of forgotten dreams.  It should be reviewed periodically to ensure the relevancy of the items. Ideally, the items should be arranged by priority to reflect the roadmap, hence making the planning of iterations more convenient. In Planbox, labels can be used to identify related items and to map items to big roadmap efforts.

The project leader (e.g. product owner) should select in advance some top-priority items from the Backlog, so that the team members can then discuss and break them down into more detailed tasks during the iteration planning meeting. While usually this is done by stacking items at the the top of the backlog, in Planbox, you an keep your selection organized by putting items in future iterations tabs.

2. Iteration Objective or Theme

At the start of the iteration planning meeting, it helps to give a sense of direction to your team. By setting a goal or theme, you’ll stay more focused when choosing together items you want to accomplish for the iteration. Moreover, your team’s efforts are more efficiently used when  concentrating on specific parts of project at a time.

3. Truthful Team Capacity Estimation

Resource allocation is hard because realistically, it is done based on a guessing game. Team capacity is only useful for planning if the submitted estimations from each team member are honest. Whether time or velocity points are used for team capacity estimations, it’s important to have a reference point to base estimates on. In addition to truthful personal estimates, team members must also define and agree upon the completion criteria of items. In all, the team should agree that the chosen items are possible to accomplish during the iteration.


4. Anticipation of Roadblocks

As team members take ownership of several items for the iteration, it’s important to discuss the potential obstacles that each can encounter, especially if there are dependencies. On the other hand, anticipate that sometimes things can go very smoothly, so include a few extra challenges that your team to start to work on, giving them a preview of the next iteration.

 
 
 

In sum, as it is advised to do for most meetings, show up prepared, begin with objectives, discuss truthfully and conclude with a direction for the next meeting. Meetings easily become tedious and frustrating if people feel that they are a waste of time. With these 4 elements there to help everyone stay on topic, iteration planning meetings can occur more efficiently.

 What other elements do you think are important? Please share in the comments below.

 
 

Coming up next week: 

How to optimize the usage Roles in Planbox

line

Planbox Tips: 5 Benefits of Iteration Reviews and How to Plan Future Iterations

Monday, September 17th, 2012

After determining the master plan of your project, it’s natural to just dive in and keep going until the finish line. But beware! Reviewing your plan as you go has its benefits; it could save you a lot of trouble and even help you increase effectiveness.

In this edition of Planbox Tips, we’ve picked out 5 top reasons as to why a review after each iteration is a healthy thing to do, before continuing to plan iterations ahead. Then, see some shortcuts for the Future Iterations Tab.

 

5 Benefits of  Doing Iteration Reviews:

  1. Build team morale:

This time allocated for the whole team to get together is the perfect moment for each member to showcase what has been accomplished during the iteration. Even if it is the time to also see which items have not been completed, it’s important not to stay stuck talking only about that. Your team members should use this time to communicate and to encourage each other.

  1. Keep focus on priorities (short term planning)

Breaking the project plan into smaller bites makes it easier for the whole team to attack the pie together. While reviewing what has been done in the past iteration, it is a good time pick out what are the few accomplishable steps for the next iteration. Plan on the short-term so that you can succeed on the long-term.

  1. Increase flexibility with changes

By constantly keeping an eye on what has been accomplished and missed, you can anticipate changes more effectively, whether it is preventing issues from happening or taking a complete shift in direction.

  1. Reduce costs

Because you are alert on your project’s progress, you can save costs by avoiding mistakes or by applying changes to eliminate extra work.

  1. Give a clear direction to your team

In sum, going over the progress of the project with your team together puts all the team members on the same page. By being aware of every step that everyone has taken together, it will give your team better ownership of their work and give them a better visibility of how their actions are contributing as a whole.

If you have more, please share them with us in the comments section!


How to Plan Future Iterations in Planbox
You can move  items from your backlog into the recently added “Future” tab on the Items Board in the Items & Tasks Page in Planbox. You can even create several iterations ahead!

 

Planbox Agile Project Management Tool Software Application Plan Future Iteration Sprint

 

A few handy shortcuts for planning:

  • Use the Blue Arrow shortcut at the extreme left of individual items to move items from an iteration to another. The blue arrow icon appears when you hover your cursor over an item.
  • Simply drag and drop items into different Iteration Tabs.
Planbox Agile Project Management Tool Software Application Move Items Shortcut


More blog posts about planning iterations are coming up. Stay tuned for:

  • Planbox Tips: Using templates to plan your iterations
  • Planning with hours versus velocity points
line

Prioritizing Priorities – nothing redundant about that

Friday, April 15th, 2011

When it comes to planning, whether for time, projects or personal matters, I find that what people struggle with the most is Prioritization.

The are over 8 000 books on Prioritization in Amazon, which I find to be a good indicator of the size of the struggle. That being said, I’ve ran across the pain of managing priorities myself or rather the pain of (NOT) managing them.

When I was in college, I ran a small business to pay for my tuition and I had to manage a couple hundred clients while keeping up to date on school work, friends and my personal life… a lot to handle for a 20 year-old kid.

In order to keep my priorities straight, I tested out multiple systems to manage my time properly and weight where my efforts would turn out the best value.

I came across the “7 habits” time Management matrix, which was highly suitable for me at the time. As a graduated college and started my professional path, I quickly found that Managing Priorities gave me an edge on co-workers.

The Matrix is pretty self-explanatory. You’ll need to face some truths you don’t want to see, but you basically want to spend all your time on Q2, minimize Q1 and eliminate Q3 & Q4 altogether.

Now working as Product Manager in a PM-oriented environment, I realize that when it comes to the Product Backlog, similar issues are faced daily but on a much, much bigger scale. Trying to apply the 7-habits matrix to the Product Backlog helped a lot. However with over 1500 items in the backlog it quickly becomes a mess.

We decided to add a few other filters to weed out unimportant/unvaluable items from the backlog, which introduced the Estimated Time, Point Value and Business Value (my personal favorite). Whether you’re agile or not, using points or time as a measure of effort (you do manage effort right?) – this makes sense.

With all of these fields filled out, which – let’s face it – doesn’t take that long, we could officially say we had our priorities straight. In the end for Planbox it all came down to Value/effort ratio.

The more value for the effort needed, the higher on the priority list. Since unimportant features bring no business value, these quickly fall at the bottom of the list and it’s something everybody on the team – stakeholders included – can relate to.

line