GX Technology : Mar 28, 2016 - Axis self assessment

Something went wrong with this Survey, it only recorded one response because I sent to a single e-mail address.

It does not have any conclusive information.

Sprint Planning

–	Always	Usually	Rarely	Never	Total–	Weighted Average–	Last Review	Discussion Required	Comments
– Our stories are confirmed in a ready state before being brought into sprint planning	0.00% 0	100.00% 1	0.00% 0	0.00% 0	1	4.00	3.50
– Our Sprint planning results in a populated sprint planning backlog and a sprint goal	0.00% 0	100.00% 1	0.00% 0	0.00% 0	1	4.00	4.50
– Our sprint planning ends with a commitment to an achievable sprint goal	33.33% 2	16.67% 1	50.00% 3	0.00% 0	1	4.00	3.83
– Our Sprint planning is informed by the team's own velocity data	0.00% 0	0.00% 0	0.00% 0	100.00% 1	1	2.00	2.67		We do not track velocity. We need to track the estimated Story points/Time as well as the actual. We do not understand how much work is involved in integration support Have a Scrum training session How can we track injections - Add Labels How do we properly Story Point

Our Sprints...

–	Always	Usually	Rarely	Never	Total	Weighted Average	Last Review	Discussion Required	Comments
– ...are a consistent duration of 4 weeks or fewer	0.00% 0	100.00% 1	0.00% 0	0.00% 0	6	4.00	4.83
– ...are time boxed: duration is not extended	0.00% 0	100.00% 1	0.00% 0	0.00% 0	6	4.00	4.83
– ...consistently conclude with the Development Team delivering what was committed to during sprint planning	0.00% 0	0.00% 0	100.00% 1	0.00% 0	6	3.00	3.17
– ...have clear, up to date, highly visible daily progress information (such as a sprint burn down chart)	0.00% 0	0.00% 0	0.00% 0	100.00% 1	6	2.00	2.83

Sprint Review

–	Always	Usually	Rarely	Never	Total	Weighted Average	Last Review	Discussion Required	Comments
– Our Sprint Reviews only includes Product Backlog Items (PBIs) that have been complete to team definition of Done	0.00% 0	0.00% 0	100.00% 3	0.00% 0	1	3	3.17
– Our Sprint review demonstration is of working, tested software that has been integrated into the mainline	0.00% 0	50.00% 3	16.67% 1	33.33% 2	1	2	3.17
– Feedback from the sprint review is collected, and the Product Backlog is updated as needed	16.67% 1	50.00% 3	33.33% 2	0.00% 0	1	4	3.83

Sprint Retrospective

Product Backlog 

–	Always	Usually	Rarely	Never	Total	Weighted Average	Last Review	Discussion Required	Comments
– Our Product backlog is ordered based on value and is estimated	0.00% 0	100.00% 1	0.00% 0	0.00% 0	1	4.00	3.67
– Our product backlog is estimated by the team using a structured estimation technique (e.g. Planning Poker)	0.00% 0	100.00% 1	0.00% 0	0.00% 0	1	4.00	3.50
– Our team has a well understood approach to refining PBIs to ensure they are ready for Sprint planning	0.00% 0	0.00% 0	100.00% 1	0.00% 0	1	3.00	3.33
– Our product backlog is the sole source of all work that the team needs to complete (i.e. includes defects, functinoality, refactoring, and so on)	0.00% 0	100.00% 1	0.00% 0	0.00% 0	1	4.00	4.17
– Refinement sessions are held throughout the sprint	100.00% 1	0.00% 0	0.00% 0	0.00% 0	1	5.00	3.33

Definition of Done

Product Owner

 

–	Always	Usually	Rarely	Never	Total	Weighted Average		Discussion Required	Comments
– Our Product Owner is readily available and actively involved in all sprint ceremonies	100.00% 1	0.00% 0	0.00% 0	0.00% 0	1	5.00	4.83
– Our Product Owner ensures that the Product Backlog is ready for Sprint Planning	0.00% 0	0.00% 0	100.00% 1	0.00% 0	1	3.00	4.33
– Our Product Owner acts as the "Voice of the Customer" integrating requirements from all important channels	0.00% 0	100.00% 1	0.00% 0	0.00% 0	1	4.00	4.33
– Our stories are written from the user's perspective	100.00% 1	0.00% 0	0.00% 0	0.00% 0	1	5.00	4.20
– Acceptance criteria is complete and well written	0.00% 0	100.00% 1	0.00% 0	0.00% 0	1	4.00	3.17

 

Scrum Master

Additional Comments

We should define Done.

Themes

• Definition of Done
• Stories/Breakdown
• Planning for Injections

Actions: