Awesome, let's start

Awesome, let's start

Génial, commençons

1Do you have a Scrum Master, Product Owner and Development team in your company?

2Does the team organize the work in 4 weeks or less long sprints to deliver working and tested software?

3Do you organize sprint planning meetings before each sprint?

4Do you use sprint backlogs during the project progress?

5Do you organize daily stand-up meetings (daily Scrums) to discuss the current project aspects and progress?

6Do you hold a sprint review at the end of each sprint (usually a four- hour meeting for a month Sprint)?

7Do you organize retrospectives for your team after a sprint review to discuss issues and possible improvement actions?

8Is the development team cross- functional, having all necessary skills to create a product?

9Is the number of development team members between 3 and 9?

10Do you have a transparent definition of “Done” that makes possible for every team member to assess their own work as complete?

11How often are the development team members in your organization using the stand-up daily meetings to report their tasks progress to the Scrum Master?

Always Often Sometimes Rarely Never

12How often does a development team member get ahead of other team members, for example a developer getting ahead of a tester?

Always Often Sometimes Rarely Never

13How often does the development team struggle to meet the compliance documentation initially agreed and experience difficulties to stick to it, thus cannot deploy the software?

Always Often Sometimes Rarely Never

14How often does a demo failure leads to the team`s discouragement?

Always Often Sometimes Rarely Never

15How often does the development team feel uncomfortable to risk and try new creative things during the project development?

Always Often Sometimes Rarely Never

16How often does the focus of retrospectives get on a single member accomplishment, rather than the team work progress as a whole?

Always Often Sometimes Rarely Never

17How often do you prefer to get the full picture and create a detailed story first, and after that get the development team start to work on the first project sprint?

Always Often Sometimes Rarely Never

18How often do you focus on the original release plan as initially agreed and not on the backlog and sprint progress?

Always Often Sometimes Rarely Never

19How often do you make management decisions for the development team on work related tasks, which are specific to software implementation and design?

Always Often Sometimes Rarely Never

20How often do you assign tasks to the development team members according to their role in the team?

Always Often Sometimes Rarely Never