Trying to run a Scrum project in a waterfall-dominated culture is no easy feat. Read how one CSP navigates his way through these often tumultuous waters.

Having coached traditional requirements, use cases, user stories, and agile development, I’ve fielded a lot of questions around the differences among the three major ways of specifying requirements, particularly by people migrating to user stories. To set the record straight on requirements, use cases, and user stories, I will describe each methodology and then compare the three against each other.

Here are nine habits you must break in order to be truly successful with Scrum.

The research project described in this report is three-pronged effort to investigate the issues associated with Scrum adoption. First, the practices that characterize the Scrum agile method will be stated, along with common variants. Second, projects that have adopted, or are in the process of adopting, Scrum will be surveyed to identify which Scrum practices, or variants thereof, they have implemented and the perceived value of the method. Third, factors affecting Scrum adoption will be investigated. The objective of this research is to better understand the barriers to adoption and the leverage points that might encourage Scrum to be more widely and efficiently deployed.

This article examines daily Scrum meeting" used on Agile Software Development Projects and give guidance to improve them.

This article proposes to introduce an unsystematic view of Scrum, called Organic Scrum. The concept of Organic Scrum is based on the fact that most people choose to learn by trial and error and goes deeply in the roots of any possible failure in a Scrum adoption.

Some of the most common models for collaborative requirements discovery and management in Agile/Scrum projects along with the benefits the teams obtained.

When it comes to Scrum, I'm a newb. I got my CSM certification last year and have been slowly learning how best to introduce Scrum to my organization. Recently, I started using Post-its to enhance how we use Scrum.

Maintaining a prioritised product backlog of desired functionality is a key aspect of agile software development. When working with a single product owner and a small number of backlog items, this task is easily managed. However, scaling prioritisation to multiple stakeholders and large product backlogs presents unique challenges. This paper presents a market-based approach to prioritisation that is fair, open, and scalable.

In anticipation of scope problems, the development schedule should be aligned to address the highest priority feature sets and features in early iterations, and defer lower priority feature sets and features to later iterations. To reduce risk around missing a release deadline further, the Requirements Lead should activity defer low priority features from all feature sets to later iterations. This avoids the case of being unable to release a minimally acceptable product because time was spent on low priority features from high priority feature sets when it could have been spent on all individually high priority features across feature sets.