The Latest

Laptop with code on the screen Agile Development: Focusing on the Health of Your Code[article]

In Scrum, the product owner and the ScrumMaster are supposed to drive sustainable development. But there's a third force missing from the formula: the health of the code itself. We often forget that our code is also a member of our team, and we have to be concerned about its health and well-being as much as any other team member. That means using practices to develop good code from the beginning.

David Bernstein
Branching example Picking the Right Branch-Merge Strategy[article]

A good branch-merge strategy facilitates processes among multiple developers and is the basis for any well-functioning DevOps pipeline that uses continuous integration. Let’s explore branching strategies, merging strategies, and how you can put them together in a way that’s right for your team in order to bring quality features to production faster.

Alan Crouch
Product owner standing in front of a wall of sticky notes 3 Elusive Qualities of a Great Product Owner[article]

When it comes to guiding the development of a product and ensuring you’re building what the user actually needs, a product owner is the most important hire for the team. There’s just one problem: A good product owner can be really hard to find. The characteristics that make a good product owner are elusive, but here are three qualities you should prioritize in your search.

John Yorke
Scrum team participating in a daily standup meeting 5 Ways ScrumMasters Can Enhance Daily Standups[article]

Daily standup meetings can turn into a perfunctory chore, with everyone simply going through the motions. It’s the ScrumMaster’s job to make sure that doesn’t happen and the meetings remain useful for everyone. With these five ideas, the ScrumMaster can actively help daily scrums be effective and encourage communication, transparency, and efficient delivery of value.

Ajeet Singh
Person solving a Rubik's cube Eliminate Fake Certainty and Solve the Real Problem[article]

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 with the team to define the solution, everyone can win.

Johanna Rothman John Le Drew

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.