The Scrum Development Team

The remaining members of the SCRUM team make up the development team. 0:00 These team members commit to finishing the development work of the sprint. 0:04 The team shares a definition of done, or a set of standards the team agrees 0:08 to before they accept a backlog item as finished. 0:13 We will cover the definition of done in more detail later. 0:17 The SCRUM ideal is that development team members are cross-functional, meaning that 0:20 they are flexible in the kind of work that they can do to contribute to the team. 0:24 For example, a team member may typically work as a front end developer, but 0:29 if the tasks that the team needs completed are in a different area, he or 0:34 she may take on one of those tasks. 0:38 This is desired even if it will take that team member 0:41 a little longer than someone who does it all the time. 0:44 Because at that moment, 0:47 the team's sprint goal is more important than optimizing one team member's output. 0:48 It's expected in SCRUM that any development team member 0:53 can pull a task from the sprint task board and begin work. 0:56 When there's doubt about how to best serve the team in a sprint, 0:59 team members can look to the SCRUM master for 1:03 help in identifying ways the team members can move the sprint forward. 1:05 In SCRUM, the development team represents the software engineers who write and 1:10 test code. 1:13 This is an important role because in Agile the key measure of success 1:15 is working software. 1:19 As important as the product owner and the SCRUM master are to the product and 1:20 to the team, it's no exaggeration to say that without development team members, 1:24 the team is nothing. 1:29 A humorous analogy to the role of development team members versus the SCRUM 1:31 master and product owner is a tail of a chicken and a pig working together. 1:34 [NOISE] They decide to open a breakfast place. 1:39 They're trying to think of a good name for the place and the chicken suggests, 1:42 Ham & Eggs. 1:46 The pig protests saying, the thing is, I'd be committed to the project, 1:47 where you would simply be involved. 1:52 The development team members sometimes refer to themselves as pigs 1:54 in SCRUM software development. 1:58 But there's fair argument about whether the SCRUM master and 2:00 the product owner are pigs or chickens. 2:03 Let's just say that in a good team, I think we are all pigs. 2:05