--- title: "Shu: articles" url: "https://www.5whys.com/articles/category/Shu.md" canonical: "https://www.5whys.com/articles/category/Shu" tags: [] author: "Roy Osherove" description: "Posts for the Shu stage of ShuHaRi, following the rules, with practices such as owning your team, task boards, standups, code reviews and stuck members." usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)." license: "https://creativecommons.org/licenses/by/4.0/" --- # Shu: articles Posts for the Shu stage of ShuHaRi, following the rules, with practices such as owning your team, task boards, standups, code reviews and stuck members. HTML: https://www.5whys.com/articles/category/Shu · 14 linked entries (each is plain Markdown) · Site index: [llms.txt](https://www.5whys.com/llms.txt) - [Scrum vs. Kanban attitudes](https://www.5whys.com/articles/scrum-vs-kanban-attitudes.md) (2010-06-13): A link to a post on how Kanban and Scrum differ in attitude and in how they provoke change, with a note that combining the two can work well. - [The Bus Factor - Why your ‘best’ developer is your biggest problem](https://www.5whys.com/articles/the-bus-factor-why-your-best-developer-is-your-biggest-probl.md) (2010-05-17): How to spot a bus factor of one in your team and reduce it with standups, pairing, code reviews and knowledge sharing, including the team leader as one. - [Move-Around kata for team leaders](https://www.5whys.com/articles/move-around-kata-for-team-leaders.md) (2010-02-14): A daily kata for software team leaders in which you walk around, see each teammate's current work and challenge them to find a better solution. - [IDCC talk: Beautiful teams and code leaders is online](https://www.5whys.com/articles/idcc-talk-beautiful-teams-and-code-leaders-is-online.md) (2009-09-15): A link to the Hebrew video of Roy Osherove's IDCC conference talk on beautiful teams and code leaders, plus his questions every team lead should ask. - [How to say NO by saying YES](https://www.5whys.com/articles/how-to-say-no-by-saying-yes-1.md) (2009-09-14): How a visual task board lets a team say no to a manager's urgent request by showing its real cost, letting the manager reprioritize the work themselves. - [Document Your Air, Food, and Water](https://www.5whys.com/articles/document-your-air-food-and-water.md) (2009-09-14): Travis Illig on documenting a team's air, food and water: a lightweight team FAQ on source control, builds and tools that helps new members get going. - [Spend at least 50% of your time with your team](https://www.5whys.com/articles/spend-at-least-50-of-your-time-with-your-team.md) (2009-09-10): Why a team lead should block 50% of each day as team time, and how to use the Five Whys and assertiveness to cut down on meetings that add no value. - [Step #4 - Start doing code reviews – Seriously](https://www.5whys.com/articles/step-4-start-doing-code-reviews-seriously.md) (2009-09-08): A team leader's guide to serious code reviews: what to look for, reviewing every check-in yourself at first, then training the team to review its own code. - [How to find hidden problems in your project before it’s too late](https://www.5whys.com/articles/how-to-find-hidden-problems-in-your-project-before-its-too-l.md) (2009-09-08): A pre-mortem technique for new team leads: ask the team and stakeholders to imagine the project has failed and explain why, surfacing hidden risks early. - [Making Impossible Decisions Without Panicking](https://www.5whys.com/articles/making-impossible-decisions-without-panicking.md) (2009-09-07): How a team leader can make a decision with only bad options without panicking: involve the team, weigh the risks, then run a blame-free review afterward. - [Daily Standup Meetings - Introduction and 5 useful tips](https://www.5whys.com/articles/daily-standup-meetings-introduction-and-5-useful-tips.md) (2009-09-06): How to run a daily standup meeting with the three questions, why each question matters, and five hard-learned tips for keeping it under 15 minutes. - [4 ways to discover a stuck team member, and what you can do about it](https://www.5whys.com/articles/4-ways-to-discover-a-stuck-team-member-and-what-you-can-do-a.md) (2009-09-06): Roy Osherove recalls being fired as a stuck developer and shows how standups, code reviews, test reviews and pairing help a lead spot and unblock people. - [Step #2 – Use a big visible board with post it notes](https://www.5whys.com/articles/step-2-use-a-big-visible-board-with-post-it-notes.md) (2009-09-05): How a team lead can use a big visible whiteboard with sticky notes to track tasks, expose developers juggling several tasks, and show management the load. - [Step #1 – Claim Your Territory, Own your team](https://www.5whys.com/articles/step-1-claim-your-territory-own-your-team.md) (2009-09-05): Why a dev lead must claim the team's territory: keep implementation decisions inside the team, be its single entry point, and ask why outsiders interfere. --- ## About the author **Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery. ### Sites - [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership. - [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts. - [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin. - [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model. - [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps. - [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes). ### Social - X: https://x.com/royosherove - LinkedIn: https://www.linkedin.com/in/osherove/ ### Contact - Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7 ### License Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/