project planning
Articles
 |
Using Agile for Requirements Management Charuta Phansalkar writes on the necessity of capturing and understanding requirements using agile practices. Agile, when implemented effectively, will ensure that the customer's voice is clearly understood throughout the project, which results in maximum customer satisfaction. |
|
 |
Designing Scenarios for Agile Stories The needs to improve the time to market of a quality product and adapt to a changing business environment are driving organizations to adopt agile practices in order to be competitive in the marketplace. However, a project team is bound to face difficulties if it is not trained on the fundamentals of agile. Read on to learn how to design scenarios for agile stories using a structured framework. |
|
 |
An Architect in the Agile World Jonathan Wiggs explains that in 2001, the agile process began to emerge and roles began to change. So, in the modern agile world, is there still room for the architect? If there is, how has that role changed in the last twelve years? |
|
 |
How Using Agile Can Help with Risk Management Agile methods are one way to use iterations and frequent feedback to manage risk. Getting feedback early so that you can make corrections or change expectations isn’t a new idea, but implementing a process that can give you both this feedback and the tools you need to make corrections is difficult for a number of reasons. |
|
 |
Mowing the Lawn: An Application of Agility Anthony Akins explains how he used agile methods to modify the way he mowed his lawn. Learn how any project can benefit from using an agile approach and how large projects can be broken down into smaller chunks, each complete and with value. |
|
 |
How to Know When Things Are Really Done Do you know when your work is done? Are you sure your feature is done? How about your release? Do you know when it’s done? Leyton Collins has some suggestions for you, your team, and your organization on how to know when things are really done. |
|
 |
An Agile Approach to Thinking Up Front about Requirements Thinking about interacting with the customer at the start of the project? Who would argue against that? Well, it depends on what you call it. It also depends on whether you then do it without the benefit of the rest of the project team. Here, Ulrika Park helps us see what an agile approach to thinking about the requirements might look like. |
|
 |
Fix Your Agile Project by Taking a Systems View Kathy Iberle writes that when working on a project, you should take a systems view, which allows you to see the whole development system at once. When you put on your “systems view” glasses, you’ll see that you need to deal with the whole system, not just a single team’s part of it. |
|
|
Building a Backlog for Legacy System Changes Kent McDonald writes that teams often assume that they cannot split their changes into small stories because the resulting stories would not provide value. What they fail to realize is that they can split these bigger changes into smaller changes and gain value by showing their stakeholders, getting feedback, and incorporating that feedback in their continued development. |
||
 |
What Position Do You Play? Micheleen Merritt explains that as an agile coach, you need to take into account all of the participants of a team, not just the developers. If you aren’t acknowledging the quality assurance analysts, business analysts, and product owners, you aren’t coaching the whole team. |
Pages
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.