Requirements Management and Quality Assurance Track
Gary McCants &
Chris Tullier
In this collaborative session, Chris Tullier and Gary McCants will present a bit
of theory and a bit of technology about requirements for agile development. For years User Stories have been a popular
way to indicate requirements, but only recently have acceptance criteria emerged
as important adornments to them. Come
prepared to learn why, participate hands-on, and to see how TFS helps support User
Stories and Acceptance Criteria to make agile Teams win.
Download PDF
Ken Howard
The key ingredient to successfully developing quality software is communication.
Through the years, lines in the sand have been drawn and battles have been fought
over the appropriate forms and level of detail to use when documenting requirements
specifications.
Describing the structure and behavior of a business domain is very closely aligned
to the skills of successful mapmakers. Magellan, Vasco De Gama, and Columbus all
demonstrated the value and usefulness of quality maps. While their stories about
their travels were probably fascinating, the maps developed by their cartographers
provided sustainable concrete records that were informative and helpful to others
who followed.
As you navigate the treacherous waters of software development, quality maps can
accelerate the journey and raise the quality of the results. In today’s information
intense business world, there are limits to how much information can be communicated
productively. Proper choices can lead to quality results, while poor choices can
lead to disasters. There are a plethora of tools and techniques available to today’s
business mapmakers. In this presentation, demonstrations and examples will be provided
of a variety of techniques, along with a survey of popular tips and best practices.
Ed Grannan
What is Quality? What are its measures? When can and should it be measureable? We
know that an agile project’s highest priority is to: “satisfy the customer through
early and continuous delivery of valuable software”. We will explore when and where
quality can begin to address the quantitative value of deliveries during the life
of an agile project. Collaboratively working with the Product Owner to ensure that
the Business Owners receive the value they expect.
Download PDF
Gary McCants
Conventional wisdom says that ambiguity in requirements is bad.
But in an agile project it is good, at least for a while and in the right
measure. Come learn how your teams
and your customers are ultimately better served by the right amount of ambiguity.
Topics include the principle of delayed commitment, and how acceptance criteria
fit in.
Download PDF