Back

Epics and Personas – Part 3

Story-Writing Workshops

Another excellent method for collecting details about epics and user stories is to set up a workshop and invite along the users, the Scrum team, and any other relevant stakeholders. During the session, the attendees will brainstorm and provide their feedback on the list of requirements. By gathering everyone in one place like this, the time can be used productively to delve into the different aspects and nuances of the features in question, thereby allowing the Product Owner to elaborate on several user stories within a relatively short space of time.

Questionnaires

Questionnaires are useful when there is a large user population and a deeper level of detail is needed on user stories or epics that have already been defined. They should only be used as a means to further refine information that has already been collected, and not as the primary mechanism for gathering requirements.

Prototyping

A somewhat different technique that can be used to gather the specifications for a user story is prototyping. This involves creating a sample or model of what the feature will look like when it is complete. When this is produced and shown to the eventual users, what happens is that they are able to visualize the functionality in action in a much clearer way than simply talking about it. As a result, any flaws or misunderstandings are more easily pinpointed and ironed out, and there is a greater likelihood that the user story will be delivered smoothly and will meet expectations.

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 »