Common Sense Project Management Methodology


Published on

What is the right project management methodology for your context?
Recipe for successful project delivery?
How to come up with a methodology that caters to your context?

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Common Sense Project Management Methodology

  1. 1. Common Sense Project Management Methodology
  2. 2. Methodologies – Quick Overview <ul><li>Waterfall </li></ul><ul><li>Agile </li></ul>
  3. 3. Methodologies – Pros and Cons <ul><li>Pure Waterfall </li></ul><ul><li>Works well when the requirements/specifications are well defined and stable </li></ul><ul><li>In theory, more deterministic in nature </li></ul><ul><li>Detailed planning helps map out all dependencies ahead of time – especially important when team is distributed and matrixed </li></ul><ul><li>Works well when team management is highly structured and process oriented </li></ul><ul><li>Not well suited to handle changes along the way </li></ul><ul><li>Testing in the very end is risky </li></ul><ul><li>Pure Agile </li></ul><ul><li>Works well when requirements are not ‘ALL’ firmed up, but team can start on some </li></ul><ul><li>Not very deterministic on what gets delivered on <x> date or when <y> feature gets delivered </li></ul><ul><li>Assumes very high collaboration (co-location) between the different teams (product, design, tech, qa) </li></ul><ul><li>Equipped to handle changes with minimal disruption to overall flow </li></ul><ul><li>Assumes a more experienced self-managing team </li></ul><ul><li>Focus on QA from early on – good for quality </li></ul>
  4. 4. My Context - Typical Software Development Context <ul><li>Most of the projects start with some product idea and a somewhat firm launch date for marketing/PR reasons or a product idea that gets tied to a date very quickly </li></ul><ul><li>In order to commit to a date, we will need to do some upfront scoping, estimating and planning to inform the team size, dependencies, budget, etc – So, pure Agile doesn’t work. One of the trio (scope, time, budget) needs to be fully negotiable for Agile. </li></ul><ul><li>Too often, we have to start a phase before the previous one ends (start development before design completes) – means need to be able to absorb changes and additions to scope – So, pure Waterfall doesn’t work. </li></ul><ul><li>Lot of conflicting priorities pop up – not always structured and need to be able to handle some chaos/changes along the way </li></ul><ul><li>Team is not always experienced at the same level - so, need to account for ramp-up and varied degrees of team management </li></ul>
  5. 5. Methodology in my context - Hybrid <ul><li>Need to do waterfall like upfront scoping, estimation and planning </li></ul><ul><li>Need to be agile enough to absorb “some” changes along the way </li></ul><ul><li>Need to focus on Quality early for better quality </li></ul><ul><li>Need to be able to tailor the methodology to a project’s context (as needed) </li></ul>
  6. 6. Hybrid - Common Sense Methodology <ul><li>This is the Hybrid methodology that works in this context. I am sure many others use this or some version of this – It is just Common Sense </li></ul>
  7. 7. Recipe for Success <ul><li>Successful Project Delivery = </li></ul><ul><li>Understand the ‘What, How, Who’ </li></ul><ul><li>+ </li></ul><ul><li>Solid hands-on experience in PM competencies </li></ul><ul><li>+ </li></ul><ul><li>Domain Experience </li></ul><ul><li>+ </li></ul><ul><li>Lots of Common Sense and Discipline to pick the right aspects from the prescribed ‘methodologies’ to cater to your context </li></ul>
  8. 8. Feedback Welcome <ul><li>Are there things I can do differently in my context and be even more successful? </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.