Skip to main content

Priorities & MoSCoW

One of the most important tasks a PM has on a software development project (maybe in all projects) is setting priorities. Usually time and money is shorter than everybody would like and you have to choose what to develop and what not to develop. It takes communication skills, a lot of negotiation and, at the end; everybody is a little bit frustrated…

If your team is developing software iteratively and incrementally (and you should… but that’s a theme for another post), you have to prioritize each iteration sub-scope.

To make scope more clear, at my company we adopt the MoSCoW list. I believe it originally has roots on DSDM (although it is used similarly on SCRUM, UP and it has elements of Cockburn’s actor-goal list) and it is a very powerful tool.

Simply stated, it is a list of requirements (or actor-goals, or use case titles…) each one prioritized with a letter MSCW (Must, Should, Could and Won’t – that’s the origin of MoSCoW list name). I simplify the explanation to my clients, key-users and team:

  • Ms and Ss: are the scope for this increment;
  • Cs and Ws: will be discussed for the next increment. These are the items “left to the next increment” in the last increment and the new items “discovered” during last increment;
  • For the Ms and Ss, it is interesting to maintain 50%-50% in the classification. If everything is “more important”, than nothing is “more important”. Rarely I can achieve this perfectly, but the discussion is what is important for the team.
  • W’s: are the “no, never” or “someday, maybe… but at THIS MOMENT it is almost impossible”.

I recommend you reading a more formal definition in Wikipedia.

My tips on MoSCoW lists:

  • Be explicit on leaving C’s and W’s out of scope… for now (for this increment);
  • Don’t loose your users’ trust – you should review C’s and W’s before every new increment;
  • Treat changes on these classifications as scope change requests in a good and classic PMI way. You should formalize it and communicate it.

MoSCoW lists are VERY powerful. I work with professional of many countries and in many continents. I can attest it works well in many situations and clients. This tool helps your team in setting the project scope, leaving priorities clear, and in communicating these priorities.

Comments

Post a Comment

Popular posts from this blog

Tools for blogging

Maintaining a blog sometimes is a difficult task, specially when you’re in the middle of a battle. It takes discipline and the belief that your ideas and experience could improve someone else’s. There are some tools to assist you in writing a blog but I discovered that my old palm and a simple sheet of paper can work better than new editors or browser plugins that allow you to post from any webpage. Maybe I’m facing a corollary of KISS principle (keep it simple, stupid). On the other hand, reading many blogs is almost impossible without a specific tool. I had a good time using RSSOwl and now I’m using GreatNews , both are free. I tried the Google Reader version of it but I’m usually offline when reading the blogs – usually at the airport. I also use my iPod to follow podcasts. If you’re a project manager I recommend Jerry Manas Project Results Podcast . What are you using to follow my blog? Leave your experience as a comment here!
Post a Comment
Read more

TimeTo

I just licensed a new software for my personal organization system: TimeTo . It tries to conciliate your schedule with you to-do list, automatically scheduling your tasks based on priorities and deadlines. It has helped me in maintaining the concentration on what I’m doing at each time and how much time I spend on doing each type of task. Additionally, I have a very powerful way to complete my timesheet. I can tell you exactly what I was doing at a specific time in the past. It is not easy to conciliate it with GTD and I still keep my lists on my Palm but I have improved my focus and I’m achieving more. I suggest you to give it a try.
1 comment
Read more

Running a lot...

I’ve been running a lot recently. My team received a lot of attacks… I guess the best piece of advice after this period is: be diligent and systematic on the project basics. I mean, you should focus on project progress and in keeping scope clear, setting and updating a workplan, keep writing your progress reports. Even when it looks you should focus on other things, do not forget to keep the basis of project management. After the turbulence, nobody will remember that you were doing the “other things” and they will ask for the basic items. More than that, even during the turbulence, your team depends on you to keep project progress. Go back to PMBOK if you don’t understand what basis is. PMBOK is not perfect but it contains a solid foundation. Agile PM only means (to me) that you don’t have to create and sign formal documents. But you have to materialize this tools: post-its, whiteboards pictures (read previous posts) work well enough.
Post a Comment
Read more