This video discusses the groups dynamics that hinder self-organization in an Agile team, seen from a behavioral perspective and presents techniques to loosen the blocking dynamics.
Articles and videos on creating and managing cross-functional Scrum teams: scrum master, product owner and development team.
Your agile team has built great software, only to find out it cannot work in production? Agile has taken the development community by storm. It has improved our everyday lives. It enables us to build great working software in all kinds of environments. But for many companies, covering the last mile, bringing an application into production is the biggest obstacle to being truly agile. Prescribed processes and skill-sets in operations lag behind a decade. We have created cross-functional teams, excluding one of the most important aspects of of software – it needs to run in production!
“An adequate ScrumMaster can handle two or three teams at a time. If you’re content to limit your role to organizing meetings, enforcing timeboxes, and responding to the impediments people explicitly report, you can get by with part time attention to this role. The team will probably still exceed the baseline, pre-Scrum expectation at your organization, and probably nothing catastrophic will happen.
in this blog post, John Piekos explains how the ScrumMaster and Product Owner roles in Scrum are much more demanding than the Project and Product Manager roles of traditional project approaches. With frequent “potentially shippable product increments”, he believes that full-time effort is required from all members in order to be successful.
The five stories presented in this article, mostly based on real life, might help you see how Agile can become mechanical and what you should do about this. You will also learn some solutions that could help to solve all five symptoms. We need to allow people to act like people and not try to force them into a machine model that we have created for them.
This video explores the creation of a performance system that not only adheres to Agile principles, but actively promotes maturity in applying them to the delivery of measurable business and user value.
In this blog post, Whitney Johnson shares four simple steps to build trust with your collaborator.