Articles

Articles

Agile Superpower #3: Watch the Work, Not the People

This is the third installment in a series on Agile Superpowers. Read Agile Superpower #1: Focus on Collaborative Teamwork and Agile Superpower #2: Reduce WIP to the Most Important Work for more. Does your agile team still use the same old three questions in your standup? If so, you’re not alone. Those questions focus on each individual,

Articles

Agile Superpower #2: Reduce WIP to the Most Important Work

When agile teams master collaboration, that first agile superpower, they often discover they deliver more features faster. That’s great. However, once the team starts delivering features faster, people ask more of the team. Managers, the product owner—everyone wants more from the team. Worse, those people want more now. Even with collaboration, the team can’t deliver

Articles

Agile Superpower #1: Focus on Collaborative Teamwork

Agile teams have all kinds of ways to deliver value faster, both to verify that the team understands what the customer wants, and to verify that the product works the way everyone expects. The team can slice the stories smaller. Or, it can spike the work to create experiments and learn from them. But every

Articles

Distributed Agile Approaches Optimize for the Team over Individuals

Summary: Consider how your team currently organizes: for resource efficiency, optimizing for the individual; or for flow efficiency, optimizing for the team? Successful agile teams—distributed or not—should collaborate to optimize the flow of work through the team. This approach lets you understand your capacity, learn together, and deliver more effectively. Too many “teams” feel like

Articles

Saying No to More Work

If you are like most people I know, it doesn’t matter what approach you take to your projects—your manager has too much work for you to do. Instead of a potential career-limiting conversation, frame the conversation so you can show your manager you’re considering his or her perspective. Here are some options for how to

Articles

Distributed Team Workspaces Start With Hours of Overlap

Dave, the tech lead, was trying to use an agile approach with his team. Four of the people worked together in a team room in Waltham, Massachusetts, a Boston suburb. Two people worked from their homes in New Hampshire, and one person, the product owner, worked from her home in Indiana. Their agile approach wasn’t

Articles

Eliminate Fake Certainty and Solve the Real Problem

Summary: Too often, customers have a “fake certainty” about the problems they want to solve. They might not have defined the real problem, but they have frequently defined the solution anyway. The risk is that we might build the wrong thing. When the product owner works with the customers to define the problem, then works

Articles

For Distributed Agile Teams, It’s Not All about the Tools

Summary: Many managers and distributed team members think that if they just had the right tools, they could make some agile approach work. Maybe, but tools only enhance the work of a collaborative agile team. Before you select tools, make sure you have people who can work together and have enough skills and capabilities for

Scroll to Top