Requirements

Articles

Man surrounded by sticky notes Streamline Your Agile Requirements by Avoiding Bloated Backlogs

In agile development, a bloated backlog results from teams accumulating huge lists of requirements, usually in the form of user stories. Retaining every possible story for building the product weighs down the backlog while squeezing (or obscuring) the highest-value stories. The best way to help minimize this risk is to optimize the time spent defining and refining the product priorities.

Michelina DiNunno's picture Michelina DiNunno
Clock Estimating Cost of Delay in Agile Projects with Time-Value Profiles

The cost of delay for releasing a product can be due to many factors, but that value loss can seem like an abstract concept. Attaching hard numbers to a release timeline in the form of a time-value profile helps the development team and business stakeholders have a conversation about how long they have to build a product and when it would be best to enter a market.

Allan Kelly's picture Allan Kelly
Releasing SMURFS Instead of MVPs, Maybe We Should Be Releasing SMURFS

The term minimum viable product, or MVP, has come to be misunderstood and misused in many organizations. It doesn’t mean you should be releasing half-baked, barely feasible software. Instead, you should be thinking of your product’s capabilities as a Specifically Marketable, Useful, Releasable Feature Set—or SMURFS!

Matthew Barcomb's picture Matthew Barcomb
ladder up into the clouds 4 Secrets to Successfully Scaling Agile Tech Teams

There comes a time for every successful tech team to expand. But how do you scale in an agile way without losing productivity? Here are four secrets to successfully managing this transition, from deliberately choosing an incremental growth process to hiring new team members and retaining efficient communication.

Debbie Madden's picture Debbie Madden
Failure Next Exit sign How to Guarantee Failure in Your Agile DevOps Transformation

Many organizations make the same agile and DevOps scaling mistakes year after year, then attempt to rectify them by putting together a great new strategy—only to miss the reasons causing the failure. If you want to refuse to evolve and, as a result, cause your organization’s agile and DevOps transformation efforts to deliver zero business value, be sure to follow these seven antipatterns.

Mik Kersten's picture Mik Kersten
two arrows merging 5 Steps to Successful Process Management in Mergers and Acquisitions

When going through a merger or acquisition, capturing the critical processes of both parties is a key to success. Including everyone in the planning helps ease the impacts of change and develop ideas for the future. Here are five steps to assist with process management and create a new organization that is greater than the sum of its parts.

Ivan Seselj's picture Ivan Seselj
caution sign Proactively Planning for Risks to Your Agile Project

Being aware of risk is good project management common sense. But to address risk quickly and effectively when you encounter it, the best method is to establish clear, agreed-upon, communicated responses to risk before it even happens. Dave Browett suggests some tactics to mitigate and confront risk you can use with your team.

Dave Browett's picture Dave Browett
increase ROI diagram How Being Agile Can Maximize Your Return on Investment

There is more to calculating ROI than a simple equation. It can be affected by risk, time, and other factors—including whether your team is agile. Releasing software immediately after coding and testing accelerates feedback cycles, minimizes the cost of delay, and increases return on investment. Allan Kelly tells you how.

Allan Kelly's picture Allan Kelly
money and a clock The Effect of Time on Value in Your Agile Projects

Using effort estimates as the only criteria for deciding whether work is undertaken could be leaving money on the table. Considering value—in particular, the effect of time on value, as in whether there is a cost of delay—makes for more intelligent conversations and better decisions.

Allan Kelly's picture Allan Kelly
user story card Simplify Your User Stories: Make Them Independent

Writing independent user stories seems simple, but it is actually difficult to do well. There are often parts of some stories that are dependent on other stories' functionalities, so it's not easy to keep them separated. Kris Hatcher relates how his team wrote and scored stories to keep them independent but still meeting acceptance criteria.

Kris Hatcher's picture Kris Hatcher

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.