| |
|
|
|
|
| |
|
|
| SPONSORED BY: Urban Code |
 Build and Deployment Automation for the Lean Economy
In good economic times teams attempt bold experiments that promise to take them to new heights of productivity. In lean times like these, any new investment needs to address immediate pain and show immediate payback. But the ever increasing need to do more continues.For build and release teams the demands come from all directions but adding headcount is likely not an option. This need to keep costs fixed while adding capacity makes improving efficiency key. Lean Software techniques focus on reducing waste, allowing you to deliver more in the same time and for the same cost.
Click here to learn more.
 |
|
|
| MEDIA SPOTLIGHT |
Mission Critical Agility
by Jeff Norris
What can we learn about agility from great inventors like Alexander Graham Bell and the pioneers at NASA who risked everything to change the world? Jeff Norris explores key principles of agility from a fresh and entertaining perspective by drawing on inspiring stories of people who demonstrated agile work practices long before anyone had heard of a ScrumMaster.
Watch Mission Critical Agility
|
|
| |
|
|
| |
| WHAT'S HAPPENING AT TECHWELL AND STICKYMINDS.COM |
TechWell Blogs
Experts including Lisa Crispin, Steve Berczuk, and Naomi Karten have years of industry experience and are ready to share their insight and interact with you at TechWell Blogs. Join in at http://techwell.com/blogs.
@StickyMinds on Twitter
Want to get a daily dose of what's new and popular on and in Better Software magazine? Follow @StickyMinds on Twitter for regular updates about weekly columns, news, forums, newsletters, and more. |
|
|
| |
|
|
| |
| AGILISM: DEFINING THE MOVEMENT |
Backlog Grooming
"Audience"
Per Scrum rules, backlog grooming is the sole responsibility of the product owner. For large software products, there will be many BAs gathering requirements and writing stories, but only one keeping the ranking of the backlog.
From "Backlog Grooming"by Rafael Alvarez |
|
|
| |
|
|
| |
| FROM THE DOWNLOAD CENTER |
Analyst Whitepaper: Twelve Strategies for Delivering End-to-End Agility
Sponsored by Serena
How should you implement agile practices to ensure end-to-end agility for IT application delivery? Read the analyst whitepaper "Twelve Strategies for Delivering End-to-End Agility" to learn how IT organizations can be truly agile across the entire enterprise. Learn how you can successfully extend agile from a core development focus to work across the entire application delivery lifecycle.
Click here to learn more |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
| BOOK REVIEW |
Making Sense of Agile Project Management
By Charles G. Cobb
Reviewed by Jennifer Flamm
Making Sense of Agile Project Management: Balancing Control and Agility by Charles Cobb is an excellent guide for anyone interested in learning more about agile project management and how it relates to a traditional development approach.
Continue reading the review of Making Sense of Agile Project Management |
|
|
| |
|
|
| |
| POWERPASS POINTER |
Magazine Archive
Designing an Agile Portfolio and Program Coordination System
by Arlen Bankston and Bob Payne
Scaling agile to the enterprise can be challenging once you start looking at the program and portfolio level. How do you design an effective coordination system that encourages collaboration, communication, transparency and is flexible, easy to implement and rapidly evolvable? Explore key aspects of creating a simple but effective agile-ready coordination system for managing such initiatives based upon the authors' observations and experiences across widely differing companies.
Read Designing an Agile Portfolio and Program Coordination System |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
| THE AGILE EXPERIENCE |
Defining Requirement Types: Traditional vs. Use Cases vs. User Stories
By Charles Suscheck
I've worked with a lot of teams transitioning to agile. In each situation, user stories always seem to be a sticking point, with a common question being, "What are the differences between traditional requirements, use cases, and user stories?" I'd like to answer this question with a description and example of each requirement type. I'll also use a running example: Imagine that we're writing software for placement firms, and one of the firms has requested the ability to search for candidates for a specific role by specialty within a geographic location. For example, "I want to find all business analysts who are Sarbanes Oxley (SOX) experts within fifty miles of New York City."
Traditional Requirements
Traditional requirements are usually thought of as capabilities and constraints of the system; the key term being system. All good requirements describe what the system can do or shouldn't do, but those requirements that focus intensely on the system tend to deemphasize user interaction or business context related to the user or business. To be fair, many traditional requirements do provide context for business and users, but that is usually not the main focus of the requirement, rather it's the system that is the focus.
The difficulty with having the system be the focus is that it's easy to make assumptions about what the user wants. I've seen requirements can the source of record for the system's operation. In such a case, interacting with the business or the user while the system is being developed reverted to a series of painful, negotiated change request. The work became a matter of giving the user exactly what she asked for, which may not at all be what she needed.
This is what really makes traditional requirements tough: They're written from the system perspective. Additionally, they're often written in the context of a process that enforces change control and a contract based on the requirements themselves. Throw in an ideology that encourages written communication between the business analyst and the development team, and you've got a tough job ahead when it comes to delivering value. Changes become a series of tightly controlled negotiations.
Continue Reading "Defining Requirement Types: Traditional vs. Use Cases vs. User Stories"
Visit the Iterations Archive to find out what you may have missed in past issues. |
|
| |
|
| |
| ADVERTISEMENT |
A Guide to Branching and Merging Patterns
Software configuration management (SCM) practices are at the forefront of managing a process for a development team. Choosing the correct branching pattern can either make a good development team great, or cause confusion and pain for the development team.
Click here to learn more |
|
|
| |
|
|
| |
iterations is an extension of StickyMinds.com and Better Software magazine—and a reminder that your "online resource for building better software" is just a click away at www.StickyMinds.com. |
|
| |
|
|
| |
You are receiving this issue of iterations as part of your StickyMinds.com membership, Better Software magazine subscription, or iterations subscription. We hope this publication will be a useful and enjoyable benefit. To ensure optimal receipt of these emails, please add iterations@lists.stickyminds.com to your address book or all messages from your email white list.
SOFTWARE QUALITY ENGINEERING • 340 CORPORATE WAY • STE. 300 • ORANGE PARK, FL 32073 |
|
|
| |
|
|
|
|
|