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!

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.

Give Life to Your Product Backlog

Give Life to Your Product Backlog

 A common perception when working in Agile is, "Welcome changes over following a plan." In the Agile Manifesto, however, the phrases "Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage" still mean you need a plan to begin with.How can we express the product backlog so that we can easily provide enough planning information to management without compromising on Agile principles?

PMPs versus Agile Project Managers: Clash of the Titans

PMPs versus Agile Project Managers: Clash of the Titans

To the foreign eye, a PMP is in one corner, and in the opposite corner we have an Agile project manager. This seems to be so because each advocates a different vision of how to run a project, and even a different conception about what a project really is. The PMBok Guide has been the source for years in project management, but in the last decade Agile has gained more popularity and now seems ready to challenge the champion for the belt.But is it really true that this two are opposed, or it would be possible to find common ground? Don't miss this fight, which doesn't promise knockouts but instead may go the distance.

Blogging in Barcelona!

Blogging in Barcelona!

Couldn't make it to Scrum Gathering Barcelona 2012? Read about what CSM Elinor Buxton Slomba has to say about attending our sold-out event.

Product Backlog Ordering (Not Prioritization)

Product Backlog Ordering (Not Prioritization)

Traditionally, most systems used to track defects and work items on a development or maintenance program include the concept of priority. James O. Coplien addresses the topic of priority in his 2011 article "It's Ordered — Not Prioritized!"I agree with Mr. Coplien that the product backlog should be ordered, not prioritized — and here I present slightly different reasoning to support the same conclusion.

Displaying results 471-480 (of 815)
 |<  <  44 45 46 47 48 49 50 51 52 53  >  >|