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!

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.

The Big Lever

The Big Lever

Projects, projects, projects! You know you don't like them, but do you know why? Is there a better approach? In this article, I'll outline why we've chosen to be project oriented in the past and why pulling "the Big Lever" toward release orientation is so important in making the move toward Agile solution delivery a real success.

Working with Component Teams: How to Navigate the Complexity

Working with Component Teams: How to Navigate the Complexity

Scrum and other Agile methodologies rely heavily on a set team structure to succeed. In Scrum, you have a team, a ScrumMaster, and a product owner. These teams work on features that are iteratively developed. As explained by Mike Cohn, the teams are commonly called "feature teams." However, quite frequently...

Searching for Wings

Searching for Wings

When I set out to practice and preach Agile methods, the world looked rosy to me. A team built on qualities that are human made much more sense than a team kept together by command and control. A team where everybody valued each other's individuality and uniqueness yet functioned toward one goal in an orderly manner seemed possible.But at the runway, I realized I didn't have any wings. Why? Because stakeholders were yet to come out of the comfort zone of spreadsheets, where command and control made a lot of sense.

The Agile Alphabet

The Agile Alphabet

We all start our learning process from our own native-language alphabets. Similarly, I have attempted to create an Agile alphabet (in English) for helping new Agile enthusiasts begin their learning of the common vocabulary. This is not a bible or dictionary of Agile terms; it is a knowledge base. It can always be enhanced to achieve maximum satisfaction and an Agile match-up to the alphabet.

The Value of Release Planning

The Value of Release Planning

"When will you deliver the project?""How can you ask that question? We are Agile!""At least give me a high-level timeline. When should I expect the release?""In the future."In other words: How do we schedule timelines for a project or a product in a complex environment where the outcome of one team is required for the other teams to start their work?

Stumbling Blocks

Stumbling Blocks

Ours was a typical Waterfall team that believed to the core in the SDLC (systems development life cycle). Our requesters were always adamant about sending countless changes to us at all stages of the project flow. This led to a lot of rework, a de...

Story Points Versus Task Hours

Story Points Versus Task Hours

"Cheng, this is just a three-point story. We shouldn't take more than 30 hours to do this," one of the developers told me during the sprint planning. And a development manager once advised me, "Cheng, you must not pull in any other stories, becau...

Planning Sprints on the Rummikub Model

Planning Sprints on the Rummikub Model

I was playing Rummikub with my kids and noticed they were unnecessarily frustrated all the time. In between their own turns they spent the whole time moaning, "You've ruined my plans!" every time another player put a stone down. It was not a new ...

A Scrum Master Is Not a Project Manager by Another Name

A Scrum Master Is Not a Project Manager by Another Name

Contrary to popular belief, the ScrumMaster and project manager roles are highly different and shouldn't be confused. As more companies migrate their project management to Agile, many do so without a proper understanding of what they're aiming for...

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