Suggested Topics for Definition of Done Discussion

About Michael James

Michael James is a software process mentor, team coach, and Scrum Trainer with a focus on the engineering practices (TDD, refactoring, continuous integration, pair programming) that allow Agile project management practices. He is also a software developer (a recovering "software architect" who still loves good design).

  2 comments for “Suggested Topics for Definition of Done Discussion

  1. lina
    August 13, 2014 at 9:57 am

    Hi Michael,

    I love reading your article. It is very valuable info. Thank you.

    I have questions.How to create and prioritize PBI for ERP System Implementation? Usually ERP implementation, we can not create PBI that satisfies INVEST criteria.

    Thank you

  2. December 15, 2014 at 6:56 pm

    That point Lina, is something I´ve been asking for myself. Is it Scrum the ideal choice for personalize products such as ERPs at the implementation level? If you focus on statistics, Scrum Projects finishes on time and without loss 48% of times, meanwhile waterfall ones, are successful just 17% to 18%, so, if you add Scrum and Waterfall, your chances of sucess are around 66%. It means that you should determine which approach to use. Maybe sometimes there will be other approach instead those two. One solution I have been dealing with is to use spyral prototyping and using a vertical of features, that´s to tell who can manage a specific story no matter if its tasks are dependent or not. I know it sounds contradictory with scrum principles but you can divide the implementation Project in deliverables like Sprints, then use cells or isles of specific stories, rearrange the goals for the deliverable and let programmers to be in charge of tasks that are pat of that cycle. In such way if something is not complete, you can show something of it and be clear for which cycle can be done at 100%.

Leave a Reply

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