Back

Releasing the Product – Part 2

Defining the feature set

The product backlog contains a list of feature requirements. The requirements are written as epics which can be equated with categories. Through subsequent refinement, epics are broken into manageable sizes with user story syntax. The product owner will be responsible for refining the backlog throughout the life of the project to ensure that the user stories are well defined are correctly prioritized.

As user stories are defined it is important to evaluate whether a feature adds value to the end project, is a nice to have or is a dependency that will minimize technical debt. Nice to haves are usually prioritized lower in the backlog because there is not a direct correlation with incremental value to the business owner.

Features will evolve over the life of a project. This is where refining at multiple stages is important for the product owner. There may be a realization that a user story is too large to deliver in one sprint. In this case, that user story should be broken into smaller increments. The value of the feature is maintained by releases that are immediately usable. As a project progresses, Agile’s inspect and adapt model, makes it feasible to re-evaluate features and determine those that may no longer be required. Scope definition is flexible and can be adjusted to meet the needs of the market and learnings from earlier sprint deliveries. The product owner will group updated user stories into feature sets for effective release management.

59 Seconds Training Video

Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)

Introductory Offer: Free Course

Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)

What is this course?

This ‘Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)’ provides an in-depth understanding of the Agile Scrum Developer roles and responsibilities

You will explore the Agile Scrum project life-cycle, including how an Agile User Story is created, to how we know when it is ‘done’

This course is aimed at those with or without prior knowledge and experience of the Agile values and principles

During this course you will learn the tools needed to succeed as an Agile Scrum Developer

What will you learn?

You will gain an in-depth understanding of the Agile Scrum Developer roles and responsibilities, and you will be able to

  • Fully understand the role of the Agile Scrum Developer
  • Understand the roles involved in an Agile project
  • Create an effective Product Backlog
  • Effectively participate in Scrum Meetings such as the Daily Stand-up, Sprint Review and Retrospective
  • Identify the roles involves in the Scrum Team

What topics are covered within this course

You will cover the following topics during this course:

  1. An Introduction to Agile Project Management (Developer)
  2. The 12 Agile Principles (Developer)
  3. Introduction to Scrum (Developer)
  4. Scrum Project Roles (Developer)
  5. The Agile Project Life-cycle (Developer)
  6. Acceptance Criteria and the Prioritised Product Backlog (Developer)
  7. Initiating an Agile Project (Developer)
  8. Forming the Scrum Team (Developer)
  9. Epics and Personas (Developer)
  10. User Stories and Tasks (Developer)
  11. Implementation of Scrum (Developer)
  12. The Daily Scrum (Developer)
  13. The Product Backlog (Developer)
  14. Scrum Charts (Developer)
  15. Review and Retrospective (Developer)
  16. Validating a Sprint (Developer)
  17. Retrospective Sprint (Developer)
  18. Releasing the Product (Developer)
  19. The Communication Plan (Developer)
  20. Formal Business Sign-off (Developer)

Our Book Recommendations

We found these books great for finding out more information on Agile Scrum:

Translate »