agile requirements

Defining Ready: A Checklist for Grooming

Grooming user stories and decomposing features is not always easy. The demands to fill a sprint backlog for an agile feature team in a large enterprise are already immense, and tight project deadlines only compound the issue. Outside stakeholders may not understand the effort it takes to prepare a single …

Agile Troubleshooting: Interface Documentation

By Alex March

When an organization first switches to agile, the documentation and proper vetting of interfaces can often be a significant roadblock to successful delivery. In my own project, I have seen this borne out several times over. No more—I am seeking to properly detail data requirements in sufficient time. I have …

Welcoming Changing Requirements

By David Gardner

The Agile Manifesto is based on twelve principles (I’ve highlighted a couple – 2 and 12 – that are of the most interest for this post): Customer satisfaction by rapid delivery of useful software Welcome changing requirements, even late in development Working software is delivered frequently (weeks rather than months) …

Risky Business

By Christine Wollmuth

When you hear the terms “risky” and “invites failure,” do you imagine a successful project methodology? The debate between waterfall and agile methodologies can be found in any analysts’ meeting of the minds. The linear approach of waterfall methodology runs the project in one large cycle. Agile methodology takes the …

Navigation

Here’s the Team

agile requirements