use cases
Articles
 |
Know Your Customers: They Can Help You Write Better User Stories Too many user stories begin, "As a user …" Who is your user? Or, more accurately, who are they? Improving your understanding of the types of customers who use your software lets you see multiple products where previously, there was only one—and identifying dedicated products will help you prioritize and accelerate delivery. |
|
 |
User Story Heuristics: Understanding Agile Requirements Agile emphasizes just-in-time requirements rather than upfront preparation. The requirements person—be it the product owner, business analyst, product manager, or someone else—embodies the understanding of what is needed, and the user story represents the work that needs doing. This article details what user stories are (and what they are not). |
|
 |
The Three Amigos Strategy of Developing User Stories Developing software correctly is a detail-oriented business. George Dinwiddie writes on how using the Three Amigos strategy can help you develop great user stories. Remember, the goal is to have the work done just in time for planning and development. It should be complete enough to avoid stoppages to build more understanding, but not so far in advance that the details get stale. |
|
 |
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. |
Better Software Magazine Articles
 |
How Do You Write Good User Stories? Expert answers to frequently asked questions. In this issue, David Hussman explains how to write good user stories. |
|
 |
Building a Foundation for Structured Requirements: Aspect-Oriented Requirements Engineering Explained (Part 2) Aspect-oriented requirements engineering (AORE) is a new methodology that can help us to further improve the analysis, structure, and cost of development of software requirements. The second part of this two-part series focuses on the AORE specification techniques. |
Yuri Chernak
February 26, 2009 |
 |
Building a Foundation for Structured Requirements: Aspect-Oriented Engineering Explained (Part 1) Aspect-oriented requirements engineering (AORE) is a new methodology that can help us improve the analysis, structure, and cost of development of software requirements. AORE does not replace but rather complements any of the existing requirements methodologies. This two-part paper explains to software practitioners the AORE concept, illustrates how it can be applied on software projects, and discusses the benefits of AORE. Part I focuses on the AORE analysis techniques. |
Yuri Chernak
December 30, 2008 |
 |
Form Fitting: Patterns to Judge the Effectiveness of Use Cases You don't have to be Giorgio Armani to fashion effective use cases. Use case patterns can provide you with a vocabulary to help you describe and judge the quality of your use cases. Find out how you can use these patterns to improve your requirements modelin |
Steve Adolph
April 14, 2005 |
Interviews
 |
The "Show Me the Money" Approach to Software Development: An Interview with Michael Harris
Podcast
In this interview, Michael Harris, the president and CEO of David Consulting Group, explains his five-step Value Visualization Framework. He discusses how he came up with the idea, how it can help your team right now, and its similarities to the agile methodology. |
Conference Presentations
 |
By the Reader, for the Reader: The Wall Street Journal’s Secrets to Customer-Centric Experiences
Slideshow
Readers of The Wall Street Journal have seen many stories about companies shutting their doors after years of success. |
Sumeet Mandloi
|
 |
Behavior-Driven Development: Real-World Mind Reading
Slideshow
Imagine this scenario: Business users are excited to finally get their hands on an implementation delivery that is on schedule, (mostly) on budget, and passed rigorous testing with flying colors. Unfortunately, when working with the new app or feature, the users realize that the way they described their needs didn’t translate into what they actually needed. Sound familiar? While she may not be able to offer telekinetic mind-reading tools, Kim Tatum is convinced that leveraging a behavior-driven development (BDD) approach helps bridge the gap between domain experts and technical teams. Join Kim to discuss how natural, human-readable language ultimately creates shared accountability and reduces misunderstandings. Review how this framework is implemented on a variety of delivery projects and walk through an implementation approach and leading practices. |
Kim Tatum
|
 |
Rightsizing User Stories
Slideshow
User stories and their big brothers, epics, are an excellent way to describe requirements for a software system. They act as stakes in the ground to keep track of what the system needs to do, the type of user most interested in each feature, and the reason the requirement... |
Dave Todaro
|
 |
When User Stories Are Not Enough
Slideshow
IT organizations adopting agile development often struggle when applying agile to anything other than small, mid-sized, or non-critical applications. Because IT organizations must deal with the myriad business rules, non-functional requirements, industry regulations, and associated audits... |
Tony Higgins
|
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.