Simple win #2 Divide work into small deliverables

When projects are over a certain size, both in terms of people and elapsed time,  estimating the work, assessing progress and testing the work all become increasingly complex.

In general larger projects are very difficult to manage due to:

  • More uncertainty about the requirements still being relevant at the delivery date
  • Accepted tolerances can still be quite large as a 10% of a large number can also be large.
  • Overheads with communication channels.
  • Longer test period which hold up environments until all tests are completed.
  • Less focus to start with distant delivery dates.
  • Less known up front.

In order to counter these concerns projects should be divided into manageable “chunks”. This allows the customer to receive deliverables which provide business benefit earlier.

Within each release it’s ideal to prioritise work using MOSCOW (Must, Should, Could Won’t) so that essential work is delivered ahead of nice to have work. Difficult, risky and large work can then be prioritised within the must’s to address the risks as early as possible. Ideally you will also be working as part of a cross functional team (Analysts, Developers and testers) to further ensure the right work is developed at the right time.

One thought on “Simple win #2 Divide work into small deliverables

  1. I so hear you on the chance of beomicng overrun with ideas. Personally I’m a list maker and breaking down the goals into manageable scoped lists really helps me. I also have one notebook that is slated just for ideas and I date the idea at the top of the page as soon as I jot it down. This idea could be either an art illustration I wish to create to an idea for a blog post, etc. In avoiding the overwhelmed feeling one can have with multitasking so much with life and career by the larger goals of projects, one task I perform every six months is to create a huge list of all my open projects (work, career, home, art, etc.) and see which one’s are still operable, inactive or need to be dropped entirely. I can see with this larger list which projects have been dormant for such a long time, that I can either let it go, or review it for reactivating it. This also assists me in prioritizing those projects as well as the scoped lists of action steps.Thank you for sharing your tips!

Leave a Reply

Your email address will not be published. Required fields are marked *

+ 5 = 9

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>