ابدأ بالتواصل مع الأشخاص وتبادل معارفك المهنية

أنشئ حسابًا أو سجّل الدخول للانضمام إلى مجتمعك المهني.

متابعة

What metrics and data do you think are important to review during the SCRUM retrospective?

user-image
تم إضافة السؤال من قبل Jorge Boneu , Senior Software Engineer - Software Architect , eSinergy
تاريخ النشر: 2016/04/25
Rajkiran Nair
من قبل Rajkiran Nair , Project Management IT Specialist (Project Management Information Technology Specialist) , Boeing

There is a lot of focus on Quantitative metrics while discussing about Retrospective ceremony like Velocity, Burndown charts etc.. But I believe, Agile philosophy is more about people than processes, hence Qualitative metrics should be also included in the metrics to measure health and progress of a scrum team. Qualitative metrics may be intangible but could always be measured subjectively.. Here are few Qualitative metrics I do as a ScrumMaster:

1. Ask team members to write about sprint on Post-Its... identify a pattern in the retrospection and take corrective actions

2. Rate the sprint in a scale of 1 to 5... discuss and identify ways to improve the rating for future sprints

3. Open Appreciation board, where team member could recognize others who were supportive and helpful... More the recognitions...better the health of the project...

Philippe Binder
من قبل Philippe Binder , Senior consultant , Air France/KLM

Depending on the project but I would like to see:

  • burndown
  • velocity
  • defect count and backlog
  • test automation coverage
  • financial actuals and forecast

When we say data, it means information.and for retrospective we need transparent information which include : 1)  Verify outcome against Acceptance criteria   2)  Instant feedback on out come from stockholders in review meeting or soon after meeting. 3)  Burnt charts which show where team perform well and where it faced problems  its analysed details.4)  Maintained Impediment List which show actual hurdles manual, technical, unexpected during sprint.

Akin O'goke
من قبل Akin O'goke , AKIN O'GOKE

Set the stage, gather data, generate insight, actions. What could have been done better, what should we do more of and what should we start doing.

 

Muhammad Aamir
من قبل Muhammad Aamir , Senior Associate - Application Developer , JP Morgan Chase

Couple of things can do in term of process and stakeholders

Things to start doing

Things to stop doing

Point out issues and take suggestions to improve or resolve them

 

SAURABH JAIN
من قبل SAURABH JAIN , Manager , SAPIENT CONSULTING LTD

What went well with regards to people, relationships, process and tools

Potential Improvements

Plan for Implementing Improvements

Hosam Elkady
من قبل Hosam Elkady , Program Manager , Microsoft

What goes well

What went wrong

Area of improvement

Burn down Chart

Team velocity

Ismail Aydemir
من قبل Ismail Aydemir , Software Development Team Leader , CENTRAL SECURITIES DEPOSITORY

Team Velocity

Sprint burndown

Completed stories vs Committed stories

How many defects during develpment?

Neelesh Rusia
من قبل Neelesh Rusia , vice president , Goldman Sachs

Scrum Team shall discusson following four points:

What went well

What did went well (discuss in details about the reason, how to overcome the issue etc., time to implement)

New Idea (any new idea which can improve the way of working in Sprint, time to implement)

Appreciation (Appriciation to the team members who did a great job in sprint or helped others to achieve the tasks)

Dheeraj Ahuja
من قبل Dheeraj Ahuja , IT Delivery Manager , Ola Money

Burndown Chart, Customized Sprint dashboard.

المزيد من الأسئلة المماثلة

هل تحتاج لمساعدة في كتابة سيرة ذاتية تحتوي على الكلمات الدلالية التي يبحث عنها أصحاب العمل؟