Coming from a services company, for last couple of years we all have been fighting with clients over points , velocity and scope. This talk is about how to think beyond points and still create visibility to the clients and how we did this in our project ( which was a distributed agile project beased out of India and Australia )



1 favorite thumb_down thumb_up 4 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session


Learning Outcome

Learn how we moulded agile for our projects, and how can you do the same.

Target Audience

BA , Devs , QA , PM

schedule Submitted 5 years ago

Comments Subscribe to Comments

comment Comment on this Submission
  • Prashant Sagar
    By Prashant Sagar  ~  5 years ago
    reply Reply

    Hi Suchit,

    A very good topic indeed which constantly bothers novice to expert teams. I agree with Siddhi, this topic could actually be very useful for the general Agile community and not just to Distributed Teams. 



  • Siddhi
    By Siddhi  ~  5 years ago
    reply Reply

    This proposal might be a better a fit in the agile-lifecycle track. There are already many agile teams that don't use story points or velocity, and in my opinion, it doesn't really fit in the beyond agile track. 

  • Sudipta Lahiri
    By Sudipta Lahiri  ~  5 years ago
    reply Reply

    +1...  to Raja's suggestions.




  • Raja Bavani
    By Raja Bavani  ~  5 years ago
    reply Reply

    Suchit,   This title is very interesting.   Could you please update your proposal with a)  more learning outcomes or takeaways if any,  b) structure or outline of your presentation,  b) links to corresponding or related slidedeck, blog post, article, video clip.   

    Pl visit  to see a sample proposal  - it has all elements.    

    In addition to these, update your abstract with  project factors such as  problem domain, technology, number of team members on both sides,  life cycle (development or maintenance or other), etc., will strengthen your proposal.

  • Liked Prasanna Vaste

    Prasanna Vaste - Should we stop using Story Points and Velocity?

    Prasanna Vaste
    Prasanna Vaste
    Business Analyst
    schedule 5 years ago
    Sold Out!
    20 Mins
    Experience Report

    On Agile projects we estimate user stories in order to allow team to

    1. 1. Track velocity
    2. 2. Decide scope for the Iteration
    3. 3. Help Prioritize stories
    4. 4. Help Release planning

    But most of the time we faced issues with estimation. It takes lot of time in estimating user stories, managers tend to relate estimate to number of days it will take to complete the story, in some teams estimate is equal to deadline. Most of the teams which use story points to estimate the work face these issues. This results in lack of confidence on development team when stories are taking more time to complete.

    Here I am going to talk about better alternative for both the suppliers of software products (financially and ethically) and their customers (internal and external). This alternative is being used in real companies delivering to real customers with great effect where team uses count of stories completed in an Iteration as measure of progress. Will talk about how this alternative can be used to track velocity, prioritize stories, planning Iteration and for release planning.

    I will share some exmples from my past projects where team did not use story points/velocty but used count of stories completed in Iteration to measure progress and also as best indicator of future performance.