Richard Banks

My feedback

  1. 158 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      19 comments  ·  General  ·  Admin →
      Richard Banks commented  · 

      The most common problem with the "Development Team" name, is item #2, and organisations forgetting about the cross-functional aspect of the team.

      I personally like "Product Delivery Team" (because delivery is important :-D), and the D-team is delivering on the Product Owner's vision.

      On the other hand, Product Development Team is an incremental change to an existing name that makes it more apparent that the team needs to be concerned with "product development", not just in a group of software devs performing the activity of "development".

    • 143 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        17 comments  ·  General  ·  Admin →
        Richard Banks commented  · 

        As many others have said - refinement is an activity, not an event. Much like testing and coding are activities, not events.

        Is it possible to close this idea as "will not be actioned" (or whatever status is similar to that) and return the votes to the people who voted for it?

      • 26 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          5 comments  ·  General  ·  Admin →
          Richard Banks supported this idea  · 
          Richard Banks commented  · 

          I see two ways of expressing this:

          1. Change "For shorter Sprints, the event is usually shorter" to "For shorter Sprints, the event is proportionally shorter"
          2. Change "Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint" to "Sprint planning is time-boxed to 5% of the sprint duration. For a one-month sprint this is eight hours. For a 2 week sprint this is 4 hours".

          I'd prefer the first option.

        • 1 vote
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            8 comments  ·  General  ·  Admin →
            Richard Banks commented  · 

            As Andy said, the purpose and audience is different. Keep them separate.

            I also disagree with removing the time boxes. Time boxes exist to limit the potential for time wasting and creates an environment for focused effort. Removing the time box would be counterproductive.

          Feedback and Knowledge Base