The Latest
 |
Streamline Your Agile Requirements by Avoiding Bloated Backlogs[article] 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. |
|
 |
10 Things You Must Do to Become Truly Agile[magazine] Agile is not a state of doing; it’s a state of being. Adopting business models on value and learning how to make teams autonomous are both necessary steps to reap the benefit of agility. |
|
 |
Build One before Building Many: Learning from Agile Feedback[article] When you're working on a project and are presented with a big story or requirement, resist the urge to treat it as a single piece of work. One of the principles of the Agile Manifesto is to deliver working software frequently. This allows you to learn from what you built and make adjustments. See if you can break down the request and find a small piece of work within the big. |
|
 |
How to Adapt to the New Age of Testing and Development: An Interview with Melissa Benua[interview]
Podcast
In this interview, Melissa Benua, a senior technical lead at mParticle and senior backend software engineer at PlayFab, explains how the speed of development and testing has changed, as well as how to adapt to the new era of software. |
|
 |
The Power of Thinking Upside Down[magazine] Software developers can become bogged down trying to keep up with agile process and procedures. Get better results by rethinking your approach to balancing focus, agility, management, and testing. |
Recently Asked Questions
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.