Development team's Characteristics Question
I was going through scrum guide and found following information on it:
"Development Teams have the following characteristics:
They are self-organizing. No one (not even the Scrum Master) tells the Development Team
how to turn Product Backlog into Increments of potentially releasable functionality;"
I want to break down this info in detail to better understand it. Let me know if my following understaing it correct or not.
Thank you in advance
"Development team needs to be self-organized to the level that
- They will be working own their to discuss new user stories from backlog with Product owner during each spring.
- They will be implementing it (coding / developing / testing / deploying it to development environment)
- After approval from product owner, changes will be released to production."
But i believe this is the characteristics of the mature development team (which has been doing sprints from long time) but during initial agile implementation they have to be guided by Scrum Masters. Scrum masters needs to work with them to define the processes, remove work in progress and develop appropriate team to be independent. This is a long process and it can't just be achieved in a 1-2 sprints. Once development team goes through learning period where they understand process which helps them to reduce work in progress, improve effectiveness of their core work and defines responsibillity of each team memvers then development team start releasing their incremental product functionality."
Please let me know if my understanding is correct or i am missing something here.
> Once development team goes through
> learning period where they understand
> process which helps them to reduce work in
> progress, improve effectiveness of their core
> work and defines responsibillity of each team
> memvers then development team start
> releasing their incremental product functionality."
No. An immature team should release functionality starting from the very first sprint. As they mature, they will learn to develop and deliver greater levels of functionality more efficiently.
A "sprint" that is used for non-delivery purposes is no sprint at all. Something must be delivered that is of value to the Product Owner, no matter how small.
Remember also that the best way for a team to learn and improve is by releasing functionality under production conditions. Inspection and adaptation then occurs in the environment where the best data can be obtained.