|
Requirements Mapping Using Business Function Test Suites On this team, testers were overcommitted, avoidable defects were surfacing, and documentation was hard to find. Worse, trust and morale were low. Upgrading tools was out of the question, so the testers decided to take matters into their own hands and create incremental change themselves. Here's how a team added a new type of traceability to its requirement test case world.
|
|
|
Fitting Technical Writing into Agile Development As teams strive to move to a mature agile process, technical writers must adapt as effectively as the development personnel. This new agile process demands that knowledge dealing with software or product releases is only sparingly documented up front, making the technical writer's job of gathering information much more dependent on talking with people over reading requirements.
|
|
|
Streamline Your Agile Requirements by Avoiding Bloated Backlogs 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 Lessons Learned in Cross-Platform Development Building an app for a single platform is difficult, but designing, implementing, and testing an app targeting multiple operating system platforms can be next to impossible. The secret balances upfront design with customer feedback.
|
|
|
Storytelling Techniques for Better Requirements
Slideshow
Do you struggle with making your ideas clear and understandable to others? Does it annoy you to sit in requirements sessions for hours only to leave with more questions than answers? As human beings, we’re made for storytelling. It is a natural form of communication. So, Jeff Howey...
|
Jeff Howey
|
|
Improv(e) Your Requirements
Slideshow
Improvisational comedy—sometimes called improv—is a form of theater in which the performance is created spontaneously, in the moment. Successful improvisers learn and use a variety of skills and techniques which allow them to better extract ideas, expand on them, and make them meaningful...
|
Damian Synadinos
|
|
From Unclear and Unrealistic Requirements to Achievable User Stories
Slideshow
"What do you want the system to do?" can be a loaded question for agile teams. Ideally, the product owner gives you a product backlog with fully groomed user stories prioritized by business value, ready for team discussion and estimation. Instead, you may have the “big picture” product...
|
Jamie Lynn Cooke
|
|
Simplify Your User Stories: Make Them Independent Writing independent user stories seems simple, but it is actually difficult to do well. There are often parts of some stories that are dependent on other stories' functionalities, so it's not easy to keep them separated. Kris Hatcher relates how his team wrote and scored stories to keep them independent but still meeting acceptance criteria.
|
|
|
Estimating Business Value in the Shark Tank You can use analytical methods to assign business value to a user story, of course, but another way is simple estimation. Allan Kelly describes an estimation exercise that combines the Scrum tool of planning poker with a TV show format to add some fun. You end up with enlightening conversation and revealed requirements.
|
|
|
Business and Development: Working Together to Build Better Products Business stakeholders and DevOps teams both have to take an active approach to app development, but neither faction should have to change practices and processes in order to get their needs across. Investing the time to establish communication between these teams will drive delivery of the applications customers demand.
|
|