Module 5 - Invest Principle

Consider these three stories: <br /><br />“As a customer, I can import my documents from Dropbox.”<br /><br />“As a customer, I can import my documents from Google Drive.”<br /><br />“As a customer, I can import my documents from Amazon Drive."<br /><br />Are these stories independent?

• Yes if whatever story is done first does not significantly reduce the effort of the remaining two.
• No because the Product Owner will eventually want to develop all three stories.
• No because they all have to import documents.

The “N” in INVEST stands for “Negotiable.” Which of the following is true about this concept?.

• Although not a requirement some negotiability is preferable in the story.
• An example of negotiability would be a team dropping some Acceptance Criteria in order to be able to deliver a potentially releasable functionality.
• It eliminates the need to discuss with the Product Owner advanced acceptance criteria during an iteration
• It is a good practise for user stories that feel like a contract with every possible detail defined in advance

Ideally, we should not write a lot of developer stories. Why?

• Developers are a special class of stakeholders and writing stories for stakeholders is discouraged
• Writing stories for users, customers or sponsors is more valuable than writing stories for developers
• Most developer stories should be re-written to express the value of the story to users or customers

What are some reasons developers may not be able to estimate the size of a story?

• It is a high level story used as placeholder in the product backlog
• The story is of low priority and therefore has a lot of open issues
• The story does not express the value to the customer
• The developers might not know enough of the technologies involved

Writing larger user stories for placement further down in the product backlog is useful because?

• They capture more functionality and therefore a better representation of the product backlog

• They can be used as placeholders for later work

• Only small user stories should be placed higher in the backlog

• Minimizes the time invested in writing user stories until it is time the team will work on the story