This is the governing body for certification in Disciplined Agile.

Explore Initial Scope Feedback

<< First  < Prev   1   2   Next >  Last >> 
  • 24 Apr 2018 6:32 AM
    Reply # 6117524 on 5874515
    Scott Ambler (Administrator)

    That makes sense.  For Choose Level of Detail one of the options, the most effective in this case, is outcome driven.  We didn't specifically call out OKR though.  Perhaps we should flesh out the description for that option a bit to make it clear?

  • 23 Apr 2018 7:37 PM
    Reply # 6116796 on 6114542
    Scott W Ambler wrote:

    @Edson:

    Not sure what you're getting at with OKR.  Could you please elaborate a bit?

    The Inception phase is effectively a "design sprint", well, a bit more sophisticated than that but conceptually similar.  So that concept seems to be covered.

    For Explore Usage I could almost see feature being added as an option, but need to think about it a bit.  Task would be more of a planning thing.

    @Scott, 

    1. OKR - Objective and Key Results from Google could be applied as one possible approach. "Outcome driven. The requirements are captured in the form of high-level outcomes or goals, and there is explicit agreement to explore the details later. Outcomes are typically captured as a simple point-form list that is easily available to anyone involved with the initiative, for instance, applying OKRs - Objectives and Key Results"


  • 22 Apr 2018 2:06 PM
    Reply # 6114542 on 5874515
    Scott Ambler (Administrator)

    @Edson:

    Not sure what you're getting at with OKR.  Could you please elaborate a bit?

    The Inception phase is effectively a "design sprint", well, a bit more sophisticated than that but conceptually similar.  So that concept seems to be covered.

    For Explore Usage I could almost see feature being added as an option, but need to think about it a bit.  Task would be more of a planning thing.

  • 30 Mar 2018 9:37 PM
    Reply # 6008905 on 5874515

    Hi folks, Explore Initial Scope-> Apply Modeling Strategy(ies)

    I suggest applying "Design Sprint" as an approach to model the initial scope and solution, and User Interface Needs as well.

    Thanks


  • 30 Mar 2018 9:19 PM
    Reply # 6008901 on 5874515

    Hi folks, Explore Initial Scope-> Explore Usage

    Recently, teams in large organizations have been delivering value in three levels: Epics, Features, Stories. The fourth could be the task or other work items when a work item list strategy is being used.

    Thanks


  • 30 Mar 2018 9:07 PM
    Reply # 6008900 on 5874515

    Hi folks, Explore Initial Scope-> Choose the level of detail

    Option Outcome Driven: I suggest mentioning OKR as a possible method to achieve this goal when you choose this option. It seems to fit very well in this scenario.

    Thanks

  • 20 Mar 2018 11:30 AM
    Reply # 5989238 on 5874515
    Scott Ambler (Administrator)

    @Jerry - Good point.  I'm detecting a common theme in your feedback.  


    I've just posted an update to the excerpt.

  • 16 Mar 2018 6:59 AM
    Reply # 5981857 on 5874515

    When considering the delivery lifecycle such as Agile / Basic and in particular the Inception Phase. The Goal diagram for exploring the initial scope needs to consider scope that has been defined from a Product Management perspective and the overlaps from Product Discovery into Product Delivery. There are various ways or approaches to define scope within Product Management which then feeds onto Product Delivery. Understanding this interface or providing guidance would be helpful. This could include Business Roadmap, Epics & Features all being fed in with the Product Delivery for Inception. 

  • 06 Mar 2018 3:50 PM
    Reply # 5892865 on 5874515

    Thanks Scott. If you want me to explain how I use the testing quadrants, I am happy to do so. 


  • 05 Mar 2018 9:18 AM
    Reply # 5889685 on 5874515
    Scott Ambler (Administrator)

    @michael - I will update the text to make our thinking clearer.  We've run into several lean teams that use their task board to manage both their work prioritization as well as their work status.

    @aldo - Good points.  WRT epics = user activities and Features = user tasks, that's one approach that we definitely need to mention.  But it's not the only approach. Unfortunately all of the terminology in this space is overloaded due to differing interpretations.  For example, are features very small things, medium sized things, or very large things?  Depends on who you ask.

    As far as testing quadrant goes, what you describe sounds interesting, particularly WRT risk. BUT, it's not what the decision point is trying to get at.  Looking at the decision point closer, it seems to me that it's misnamed for what it is.  It should really be Capture Non-Functionals, not Explore Non-Functionals.  The three existing options are all about capture.  I'm updating the diagram and description to reflect this.


    I have just posted the v2 update to the excerpt.

<< First  < Prev   1   2   Next >  Last >> 

© 2013-2020 Project Management Institute, Inc.

14 Campus Boulevard

Newtown Square, PA 19073-3299 USA

Powered by Wild Apricot Membership Software