Development team. Let's look about this guy's development team and Scrum consider it as standalone self manageable unit. The optimal size of development demons grown from three to nine members. Here are the typical characteristic of development team. Accountability belongs to the entire development team. Regardless in nitros equation.

There are no titles for development team members other than developer. There should be no sub teams in Scrum development team. We have reviewed typically characteristics of development team. Now let's talk more and let's discuss the things that are true statements in regard to the development team activity or duties. It's true that they were meant to have final say on the size or the scope committed to the sprint backlog. So the weldment team should decide by themself how many product backlog items items they should take to the sprint backlog.

Of course, product owner can advice and can sort product backlog items in different order. But final say on the number of items or actual owns a slice of the scope is coming from the development team, they should decide by themself. It's through that scrum team defines a spring goal. It's pretty tricky equation here. Of course, product owner can make different orders for the product backlog items. And these will result in a different spring goal.

But there could be many reasons why a particular product backlog item could not be done at the time of the sprint, for example, due to technical limitations, and therefore it's important that an entire scrum team collaborate and decides or actually defines a spring goal. It's Drew's out there. And Tim decides by themself on the approach to get the sprint commitment done. So once again, we know that Grandmaster and product owner are part of a scrum team and they can advise the development team but once again, as a final say, and it should be done by the development team, as they should decide by themselves how they're going to execute the work. It's driven development team should discuss with the product owner all the issues and find the best solution regardless execution of the sprint backlog. So while working on the sprint backlogs are could be different problems, different issues and as the main point here is it and those problems those issues shouldn't be addressed.

And the product owner should be informed on the progress and problems that course while the development team working on the sprint backlog, so it's very important. It's true isn't the fall go forever sprint is to deliver up have potential early usable software. That's up sold the correct amount every spring development team need to deliver a piece of potential realisable software. So even if it's brand new team, we actually need to configure as an wireman, they still need to consider that they have to deliver a piece of potentially releasable software. And there should be no solid technical sprint or whatever it's called sprint zero. It's true that the daily Scrum meeting should take no more than 15 minutes regardless of the size of the development team.

It's absolutely correct. So no matter how many members in development team, you speak about three members or nine members, it's still necessary to make sure that daily Scrum or stand up takes no longer than 15 minutes. It's true the development team here falls the skills needed. So we can see their development team as self manageable unit. It was a number of people who have different skills. And altogether they should have all the skills needed to turn the product backlog item to a piece of potentially releasable software.

It's through the development team members could change. So whenever it's needed, it's possible to change as a member of the open team. But once again, we need to consider that performance degradation will take place in this case. It's through the development team is free to change it engineering practice whenever they want. They can change engineering practices within hours they want but it's recommended to use spatial events such as retrospective, when it's the best time to do this kind of change. Its chosen development team should resolve internal conflicts regardless of the nature eyes themselves.

So that's absolutely correct. The development team should Dealing with conflicts issues. But if they're struggling for whatever reasons, they can help a scrum master to our system. It's through the development team is a member of scrum team. So the ultimate team is a role in Scrum. And this role is a part of Scrum teams.

So that's absolutely correct. It's through that Scrum Master and product owner are members of the weldment. Team. So that's absolutely correct. And we already know that product owner and Scrum Master could combine two roles. So that's absolutely possible.

So wherever you the things that are true statements in regards to the development team, now let's review the things which are not correct are actually false statements. In regards to the authentic, let's talk about them. It's false statements that development team member could be a sole owner over Springbok located so you wouldn't if a particular developer completed a project backlog item from A to Z. We still consider this item as item which belongs to the entire development team, but not to a particular member of the development team is false statements of development team could change the sprint backlog if powerful stakeholder for example see all as a company are requested to change something. So it's false statement. And if something similar happens, they will appoint him should invite product owner and have the product owner to work with these particular stakeholder is false statements that development team have privileged to cancel the sprint is a sprint goal is obsolete.

We know that product owner is the only person who could cancel their sprint. So this statement is false. So that was a story on the development team. Now let's move on and let's summarize all three rules of Scrum.