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!

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.

Technical Debt for PMs

Technical Debt for PMs

Technical debt describes the cumulative consequences of cutting corners in software development, but it escapes the attention of many project managers as they focus on scope and schedule. That’s a mistake because it impacts both. Here are questions to help you ascertain the real state of technical affairs.

The Scrum Team Scorecard

The Scrum Team Scorecard

Transitioning toward Scrum practices isn't easy for every team. I've used a visual image that I call the Scrum team scorecard to help. It's a one-page "snapshot" of the level of transformation of a project team into a Scrum team. An independent o...

What Agile Is — And What It Isn’t

What Agile Is — And What It Isn’t

There’s going to be a lot more talk about Agile now that the Project Management Institute has introduced a new certification program for Agile Project Practitioners. Let’s clear up some initial confusion and look at what Agile is and is not, and why you should care.

Why Are We Doing Agile?

Why Are We Doing Agile?

Organizations and teams must come to understand why they need agile before choosing a methodology or tool to implement it. A mandate alone will not work. It is the overarching goals, values and principles of Agile that must ultimately guide teams in the adoption and adaptation of its practices.

Total Quality and Scrum

Total Quality and Scrum

In the software industry, professionals hold different views on processes. Some say processes are bureaucratic and rigid, making their lives difficult. "Why in the world does a simple software installation have to go through X number of approvals when I have such an urgent task at hand?" Others (mostly members of organizational process groups) relentlessly endorse standardized processes and talk about how the organization could be benefited by the data collected from following those processes. Project teams, though, are often unconvinced, since what the data says and what the customer says can differ.

Displaying results 511-520 (of 850)
 |<  <  48 49 50 51 52 53 54 55 56 57  >  >|