GitHub
LinkedIn
Twitter
YouTube
RSS

Managing Requirements

Managing Requirements

Course Level: Foundation

Communicating is difficult, especially when bringing together technical and non-technical teams.

In this workshop we will introduce methods for users to effectively communicate what they want from an application, while allowing for developers to specify how they provide it. We also discuss how to prioritise and estimate features collaboratively in order to deliver the most value the soonest. By providing a means to understand each team’s needs, we illuminate the role that each team member can intuitively play.

View our full training course calendar » Ask about our on-line training » Ask about our on-site training »

Book: Managing Requirements

Start Date:
Price:
Venue Details:
Time:
Duration:

Add Booking Add All Courses in this Series Ask For More Details About This Course

Course Details

  • Course Outline
  • Learning Outcomes
  • Materials
  • Prior Knowledge

Course Outline

  • Introduction to Managing requirements: A brief overview of why communicating requirements is difficult, but important
  • Writing User Stories: How can we go from requesting a feature to writing a user story which communicates all the key information?
  • INVEST: Improving user stories with more actionable detail.
  • Acceptance Criteria: Writing specific testable conditions to help define when the request is done.
  • The Product Backlog: Where do we put all these stories and who is in charge of them?
  • Backlog Prioritisation: Methods for prioritising features including MoSCoW.
  • Feature Estimation: Estimating relative complexity of features using story points.

Learning Outcomes

By the end of the day participants will be able to…

  • Understand common reasons why software teams struggle with communicating requirements.
  • Write high quality user stories.
  • Add testable conditions using acceptance criteria.
  • Understand the role of the product owner in relation to software development.
  • Understand and work within a product backlog.
  • Prioritise user stories using the MoSCoW framework.
  • Estimate user stories using story points.

Materials

Prior Knowledge

No prior programming knowledge of any kind is assumed. This course is suitable for all fields of work. Previous attendees include biologists, statisticians, accountants, engineers & students, i.e., anyone who uses a spreadsheet!

Attendee Feedback