The remaining members of the SCRUM team make up the development team.

These team members commit to finishing the development work of the sprint.

The team shares a definition of done, or a set of standards the team agrees

to before they accept a backlog item as finished.

We will cover the definition of done in more detail later.

The SCRUM ideal is that development team members are cross-functional, meaning that

they are flexible in the kind of work that they can do to contribute to the team.

For example, a team member may typically work as a front end developer, but

if the tasks that the team needs completed are in a different area, he or

she may take on one of those tasks.

This is desired even if it will take that team member

a little longer than someone who does it all the time.

Because at that moment,

the team's sprint goal is more important than optimizing one team member's output.

It's expected in SCRUM that any development team member

can pull a task from the sprint task board and begin work.

When there's doubt about how to best serve the team in a sprint,

team members can look to the SCRUM master for

help in identifying ways the team members can move the sprint forward.

In SCRUM, the development team represents the software engineers who write and

test code.

This is an important role because in Agile the key measure of success

is working software.

As important as the product owner and the SCRUM master are to the product and

to the team, it's no exaggeration to say that without development team members,

the team is nothing.

A humorous analogy to the role of development team members versus the SCRUM

master and product owner is a tail of a chicken and a pig working together.

[NOISE] They decide to open a breakfast place.

They're trying to think of a good name for the place and the chicken suggests,

Ham & Eggs.

The pig protests saying, the thing is, I'd be committed to the project,

where you would simply be involved.

The development team members sometimes refer to themselves as pigs

in SCRUM software development.

But there's fair argument about whether the SCRUM master and

the product owner are pigs or chickens.

Let's just say that in a good team, I think we are all pigs.