The Scrum Team is comprised of all skill sets necessary to create feature from start to finish. The team is comprised of the usual roles: developers, testers, business or functional analysts, technical writers and others. Scrum changes the mindset of traditional development which is to “inspect in quality” to a modern lean approach of “build in quality” instead. This requires a huge shift in mindset for all roles involved. New Scrum team members typically struggle with how to work together daily, abandoning the test/fix cycle or overly comprehensive documentation for more collaborative ways of working.
Agile teams should be comprised of multi-disciplined, empowered collaborative team members who manage their tasks from day to day. Of course, the self-managing aspect is toward a larger company goal, usually a product vision supplied by a product owner.
Do agile teams really exist at your organization as per this definition?
We’ve found that the answer to this question is a resounding “no” in many cases. You see, the definition of an agile team is the number one game-changer - most traditional organizations simply aren’t set up this way. Getting the organization to change its mindset about knowledge workers takes a concerted effort in educating and mentoring staff - managers and executives included. Without this learning component, agile teams can’t reach their full potential.
Delivers a Quality Increment
Does your team have a Definition of Done?
If not, that should be the first agenda item for your team to take care of - today!
Without a definition of what quality is for the end of each sprint and/or release, a team can flounder. In other words, it’s impossible to live up to a standard if that standard has not yet been defined.
The Definition of Done is an agile concept that helps guide teams toward feature completion each and every iteration, makes project metrics more meaningful, and enables organizational agility.