Case Study - When the estimates were accurate ..

This talk deals management's perspective into measuring progress. As an orthodox practice, many times they would like to measure it in terms of amount of work done (in hours). As part of this interesting case-study, we would explore if it is the right perspective and how it affects teams, and what scrum brings to the table.

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

Outline/structure of the Session

please find the outline structure in the abstract

Learning Outcome

- why estimation should be done in story-points
- importance of user stories
- irrational team behaviours in absence of management trust

Target Audience

Project Managers, Agile Coaches, Product Managers, Scrum Masters, teams

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Jerry Rajamoney
    By Jerry Rajamoney  ~  2 years ago
    reply Reply

    Hi Devesh,

    Thanks for the topic. I have a query.

    Is this is going to be a talk or sharing experience report? If you are going to share past experience how about adding more data points to make it more value add?

    Thanks,

    • Devesh Chanchlani
      By Devesh Chanchlani  ~  2 years ago
      reply Reply

      Hi Jerry,

      thanks for your interest. This topic is indeed about sharing experience report.
      As a suggestion, I have segregated the contents topic wise, so that they are more clear. (Please see them in bold.) Also, I have added few more data points. Please feel free to get back if more clarifications are needed.

      Thanks,
      Devesh.


  • Liked Madhavi Ledalla
    keyboard_arrow_down

    Madhavi Ledalla / Jerry Rajamoney - Deep dive into RETROSPECTIVES- how do we break the usual norms so that these reflections could be made thought-provoking ones!

    60 mins
    Workshop
    Intermediate

             Retrospectives are the primary learning, reflection and readjustment techniques on agile projects. A good Agile team is always striving to become better than before. And an effective retrospective enables the team to sieze its opportunity to improve! 

    Retrospectives enable whole-team learning, act as catalysts for change, and generate action.

    R-> Realize where you are and where you want to be

    E-> Engage the teams in fruitful discussions

    T-> Team work to build “We over I” attitude

    R-> Relish the power of Inspect and Adapt cycles

    O->Openness and Transparency to make retrospectives efficient and effective

    In my view, this is not any new concept or a jargon the team needs to really master, but yes in reality sometimes it becomes challenging to keep the momentum lively all times! Over a period of time, we see these symptoms in a retrospective. 

    R-> Repeated issues pop-up

    E-> Engrossing & Engaging discussions are missing

    T-> Team present virtually, loses trust.

    R-> Routine stuff, nothing interests the teams.

    O->Observably gets boring over time.

    To catalyse conversations among team members, retrospectives need to be viewed from a different perspective. This presentaion talks about why the retrospectives efficacy fades off over a period of time and then talks about some very interesting techniques that I used with the teams to make these meetings lively!  Teams need to do out-of-box thinking and appreciate that these short gatherings need not  be done only by using the techniques or methods prescribed in the book but could be done by quoting some situational specific examples that would make the teams really think and speak!