Articles published in 2013

The Daily Scrum -- Get out of the Routine and into the Unusual

The Daily Scrum -- Get out of the Routine and into the Unusual

I have participated in many daily stand-up meetings that are routine and mechanical in delivery and execution. Why have the meeting? I have also participated in many daily stand-up meetings that are extremely beneficial and by no means routine in delivery or execution. Again, why have the meeting?

Why Developing Software Is Similar to Visiting a Museum

Why Developing Software Is Similar to Visiting a Museum

With the experience that I now have in software development, I realized that visiting a museum has a lot of things in common with the software development world. When we start planning to visit a museum (or some kind of art exhibition), we need to take some concepts into account. Yes, I’m talking about . . .

About Being a Coach

About Being a Coach

Here are some thoughts, based on my experience, about being a coach. it's not about technology, processes, and frameworks. It's not about teaching people how to do stuff, although it helps if you can show them a new way or help them find a solution. But that is not at all the most important thing about coaching people. . . .

The Rationale for Testers to Welcome Scrum

The Rationale for Testers to Welcome Scrum

In my experience, many organizations don't facilitate testers in making the transition to Scrum and often are not sure how to do so, and therefore many testers are left in the lurch. . . .

Functional Managers and Executives Are Failing Agile Teams

Functional Managers and Executives Are Failing Agile Teams

With an ever-expanding global economy, a great deal of pressure has been placed on managers and executives to embrace Agile. Yet, with the best of intentions in mind, managers and executives often fail the very Agile teams they have created. Unfortunately, the people who fill these roles often don't realize they are failing until the talent base walks out the door. . . .  

The Code Is the Documentation

The Code Is the Documentation

If you talk to other Scrum practitioners, you'll quickly find that everyone has a different opinion about the "right" amount of development documentation. . . .

Resource Cost Versus User Story Cost -- Can We Match Them?

Resource Cost Versus User Story Cost -- Can We Match Them?

Each quarter we need to go through a funding gate review, and management always wants to know why user story cost cannot match with resource cost. I believe there are a number of reasons, and here I provide them along with suggestions for management. , , ,

Coaching Scrum Teams Through Conflict Navigation and Effective Communication Strategies

Coaching Scrum Teams Through Conflict Navigation and Effective Communication Strategies

In my previous experience as a technical coordinator, before embracing Scrum, I didn't have to go into the face of conflict very often, because team members in conflict had to deal with their issues by escalating them to their managers. I've realized that what ScrumMasters need is a "conflict management workout": a number of simple practices to keep in mind when trying to navigate conflict effectively. . . .

Agile People Management: 3 Reflective Questions

Agile People Management: 3 Reflective Questions

I have summed up my self-management experience, my understanding and practice of Agile values and principles, and the Unity of Knowing and Doing philosophy into three reflective or retrospective questions. . . .

Too Many Individuals and Interactions

Too Many Individuals and Interactions

Six members of a development team I was working with were discussing pair programming and debating whether it was right for them. My advice to the team was in line with my general philosophy about new ideas: One learns more by doing then by talking. So I suggested that we try it for a few sprints, and then review our experience. . . .

Displaying results 141-150 (of 270)
 |<  <  11 12 13 14 15 16 17 18 19 20  >  >|