Get certified - Transform your world of work today

Close

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!
 
Do We Need a Hardening Sprint?

Do We Need a Hardening Sprint?

While executing Agile projects, many Scrum teams use a "hardening sprint." . . . This article maintains that a hardening sprint is not a good idea and highlights why.

Rapid Deployment in an ERP Environment

Rapid Deployment in an ERP Environment

This paper suggests different approaches to speed up ERP implementations and support based on scope of work, standard package fit, and organization readiness.

Agile Test Automation

Agile Test Automation

Agile test automation is the application of the Agile development principles to test automation. Accordingly, there are some principles of Agile test automation. . . .

Is User Role Modeling Really Required?

Is User Role Modeling Really Required?

Any business requirement that needs to be formulated in user stories can be best justified if the writer knows the user roles for which the requirement will be mapped. To identify users, user role modeling is important.

The ScrumMaster's Courage to Be Weird

The ScrumMaster's Courage to Be Weird

Often, we need one person to be "weird" to protect the team. I believe it's the duty of the ScrumMaster to be weird in order to save the team from distractions and to educate everybody on various aspects of the system. I would like to discuss a few of these "weird" but important tasks that a ScrumMaster should perform.

Top 10 Reasons to Adopt Scrum

Top 10 Reasons to Adopt Scrum

Why should I -- or my organization -- adopt Scrum? Here are 10 good reasons. . . .

Helping Offshore and Onshore Teams Work Together

Helping Offshore and Onshore Teams Work Together

The theme of this story is a struggle to understand an offshore QA team's working patterns, and how I worked with both the onshore and offshore teams to overcome this problem.

Selecting a Sprint Length for Your Project

Selecting a Sprint Length for Your Project

When organizations are new to Agile -- or even after they've been practicing Agile for a while -- they often struggle to decide on the duration of a sprint or an iteration.

Finishing All Tasks

Finishing All Tasks

Sometimes it is apparent in software projects that not all the tasks have been completed when the sprint ends. . . . Here is list of some things that might help all of us achieve a much better outcome in our next product increment.

The Misinterpreted Developer

The Misinterpreted Developer

The term "developer" became so popular in the last decade that it became a synonym for "programmer." That's no surprise, given the way programmers welcomed the tag. However, "developer" has a broader sense in Scrum teams.

Displaying results 581-590 (of 1000)
 |<  <  55 56 57 58 59 60 61 62 63 64  >  >| 
The community welcomes feedback that is constructive and supportive, in the spirit of better understanding and implementation of Scrum.

 

Newsletter Sign-Up

Subscribe