Four Ways a Product Owner can Ruin a Scrum Team
1. Lack of Focus or Vision
2. Poor Communication Around Objectives and Results
3. Lacks Ability or Authority to Define Work Items in the Backlog
4. Lack of Respect for the Team

> Team performance, on the other hand, is far more visible. Perhaps the best way to track it is to ask, does this team consistently produce useful software on a timescale of weeks to months?

> "Input", "Output" or "Outcome" are the same level of importance. If you forget one or do not have a connection between "Input", "Output", "Outcome", it will impact the success of your product. Therefore, build the circle with a strong connection between "Input", "Output", and "Outcome", to deliver the value to the user fast enough and frequently for the experiment, and learn from your users what is essential. That is the core of Scrum

"Simplicity is a great virtue but it requires hard work to achieve it and education to appreciate it. And to make matters worse: complexity sells better."

— Edsger W. Dijkstra (On the nature of Computing Science)

"Experience is the hardest kind of teacher. It gives you the test first and the lesson afterward" - Oscar Wilde

4 Signs of an Inexperienced Developer ->

[TodayReading] The great paradox of behavior change

"When an athlete trains too hard, she ends up sick or injured. When a company changes course too quickly, the culture breaks down and employees get burnt out. When a leader pushes his personal agenda to the extreme, the nation riots and the people re-establish the balance of power. Living systems do not like extreme conditions."

Show more

rtHome Socials