Member Articles

Enjoy our extensive collection of member-contributed articles to learn how other Scrum practitioners use Scrum in the workplace.

Read about the experiences and ideas of Agile colleagues around the world, and share your own thoughts here. You can also visit Spotlight, which features blogs by experts in the fields of Scrum, Agile, and the broader business world.

Opinions represent those of the authors and not of Scrum Alliance. The sharing of member-contributed content on this site does not imply endorsement of specific Scrum methods or practices beyond those taught by Scrum Alliance Certified Trainers and Coaches.

Contribution process & guidelines

Got a story to tell or news to share? Here's an idea of what we're looking for.
Already have an article to submit? Please submit all articles directly to the editor for consideration.

Scrum Alliance Articles RSSSubscribe to our RSS Feed to be notified of new articles!

Self-Organizing Teams: What and How

Self-Organizing Teams: What and How

Do you have a self-organizing team? If so, half the battle is already won. But if not, beware: Creating a self-organizing team is far more challenging than we had ever imagined. This is especially true in today's dynamic world, where the focus of ...

Jip and Janneke Should Have Used Scrum

Jip and Janneke Should Have Used Scrum

A friend of mine asked me if I could explain Scrum to her. I'm always willing to do this, and I started out with iterations, and estimation and delivering value, and all the stuff we know and do. But she is not a developer, and she soon interrupte...

Key Arguments to Sell Scrum to Your Boss

Key Arguments to Sell Scrum to Your Boss

 Why should your boss let you implement Scrum in your organization? Things are already working, and they get their results.Well, one thing that I've noticed is always hard on the development side is to quickly respond to changes. The marketers, business, sales, and production staff usually need things to be done now, because, well, now is now and tomorrow is tomorrow.

How to and Not to Introduce an Agile Delivery Methodology Within an Organization

How to and Not to Introduce an Agile Delivery Methodology Within an Organization

The process organization at one of the largest global automobile giants delivers several hundred projects and manages several system change-and-upgrade activities, in addition to maintaining IT operations. The project delivery methodology employed...

When Do You Call Scrum "Scrum"?

When Do You Call Scrum "Scrum"?

As we all know, Agile and Scrum have become popular, and many development and maintenance projects are adopting Scrum to reap its benefits. In my organization, where we deal with multiple clients across different geographies with different organiz...

Less Is More: Why a 50% Solution Hit the Sweet Spot

Less Is More: Why a 50% Solution Hit the Sweet Spot

When feedback from your customer includes enthusiastic comments like, "This is what we've wanted for years," and your project sponsor says, "One of the greatest projects in my career!" then you know you've done something right. When this applies to a project that was at a dead end, without much trust from stakeholders and little money left only a year earlier, such results are even more surprising.

Your Client Isn't Your Product Owner

Your Client Isn't Your Product Owner

Sometimes, when an organization is adopting Scrum as its development model, the following unfortunate thing happens: A decision maker with authority over the team-to-be is trying to match existing people to each of the Scrum roles, and he or she thinks, "Product owner . . . well, that's obviously the customer."Wrong. In almost every case.

Golf and Scrum

Golf and Scrum

People say that you play golf to relax, and that to play golf you need to be relaxed. To be Agile you need to be professional, and to be professional you need be Agile.

Effectiveness of Group Code Review in a Scrum Environment

Effectiveness of Group Code Review in a Scrum Environment

The most ignored attribute of development is reviews. Many Scrum teams compromise on review tasks in order to complete their other tasks in a particular sprint. Though they plan separate tasks for reviews, they frequently ignore them. In reviews themselves, the most ignored is the code review. The shorter the sprint, the less the importance and time allocated to code reviews.I think it should be the other way around. 

Culture Shock

Culture Shock

Each Agile team creates its own culture. Moving between teams, and specifically Agile teams, is not only about different work or different team members to work with; it's mainly about adapting to different team cultures.Team culture takes time to evolve and — like any other type of culture — it will resist a change, no matter how small it is. That change can be in the form of new person (like you), or it can be in the form of new idea that you want to implement.

Displaying results 451-460 (of 799)
 |<  <  42 43 44 45 46 47 48 49 50 51  >  >|