Skip to content

Latest commit

 

History

History
51 lines (43 loc) · 1.09 KB

Prioritisation (Agile).md

File metadata and controls

51 lines (43 loc) · 1.09 KB

#csse3012

Prioritization

Helps in qualitative measurement of the project

  • How important is a feature?
    • which leads to
  • How much does it cost?
    • and then
  • When can we do it?

Prerequisites

Make [[User Stories]]


Process

  • Take story card
  • Rank them (MoSCoW)
  • Group Cards
  • Iterate

Factors

  • Important of user role
  • Desirability of story to others
  • Cohesiveness (does story relate to other high priority stories)
    • Dependencies between stories
  • Risk involved (Developer Perspective)

Strategies

  • Let customers decide the priorities
    • e.g. important to do SEO before adding About page
  • Deliver important business value early
  • Focus on Must Haves more than the rest
  • Split stories into mixed priority

Overview

  • Rank stories so high value stories are delivered first
  • Verify results against success criteria. Align with
    • system vision (Project Charter)
    • value proposition ([[Business Model Canvas]])

Next Steps [[Estimation (Agile)]]


[[Week 04a - Prioritisation.pdf]]


[[Prioritisation and Estimation (Tutorial)]]