1. MOSCOW, INVEST, DoR, DoD
1.1. MoSCoW
1.1.1. must have
1.1.1.1. Can we move forward with the project if this task is undone? – if NO, it’s a MUST
1.1.2. should have
1.1.2.1. Can we move forward with the project if this task is done a bit later? – if YES, it’s a SHOULD
1.1.3. could have
1.1.3.1. Can we sacrifice this task till deadline? – if YES, it’s a COULD
1.1.4. won't have
1.1.4.1. Can we back to it when things go better? – if YES, it’s a WON’T
1.1.5. benefit
1.1.5.1. easy to use and master
1.1.5.2. bring stakeholders to consensus
1.1.6. downside
1.1.6.1. can be inaccurate if there is a context shortage within the team
1.2. DoR, DoD
1.2.1. DoR
1.2.1.1. Definition of ready
1.2.1.1.1. Used for product owner
1.2.1.1.2. what needs to be done to a product backlog item before the team can start implementing it
1.2.1.1.3. based on INVEST principle
1.2.2. DoD
1.2.2.1. Definition of done
1.2.2.1.1. Used for software development
1.2.2.1.2. no more work need to be done before shipping
1.2.2.1.3. Can start empty but need to be filled up over time
1.3. INVEST
1.3.1. independent
1.3.1.1. stories can be started in any order
1.3.2. negotiable
1.3.2.1. gather opinions from people in the team
1.3.3. value
1.3.3.1. bring some value to the business
1.3.4. estimable
1.3.4.1. can be estimated through user story points
1.3.5. small
1.3.5.1. divide into small enough chunks of work (each US should not take more than 3-4 days to finish)
1.3.6. testable
1.3.6.1. clear acceptance criteria