L19 - Agile Scrum Process

Question 1

Summarise the Scrum Process

Answer 1

• Product backlog is dynamic and changes
• Depending on how long the project is contracted for
• List of functionalities the the system should have
  
  • They Have priorities
  • In the form of User Stories or Use cases
• Can change due to the client wanting to add or remove changes

Question 2

What is feature Priority?

Answer 2

• Based on importance and dependencies
  
  • Could Sort by Risk
• MoSCoW
• M - Must have
  
  • If these are missing project is a failure
• S - Should have
• C - Could have
  
  • Would be nice if money and time avaliable
• W - Wont have (least critical, Low value)

Question 3

What is MOSOW

Answer 3

• M - Must have
  
  • If these are missing project is a failure
• S - Should have
• C - Could have
  
  • Would be nice if money and time avaliable
• W - Wont have (least critical, Low value)

Question 4

What are user stories?

Answer 4

• POV of user
• Written on story cards and follow a simple structure
• 3 sentences in everyday langague

Question 5

What are the contents of a user story

Answer 5

• Identifier
• Priority
• Cost/Effort or time
• Story points
  
  • measure the effort
  • Dependencies
  • Complexity

Question 6

What is a sprint in the agile scrum methodology?

Answer 6

• 1 to 4 weeks (Remains the same)
• Contains a list of features
• End of sprint = potentially shippable product

Question 7

What are the different sprint meeting types?

Answer 7

• Print planning - planning what needs to happen in the sprint timeframe assigning user stories and delegating tasks
• Sprint Review - End of spint which can contains a
  
  • Product demo to client
  • Feedback on completed work
  • Feedback on future work
• Sprint Retrospective
  
  • Meeting after review
  • What went well
  • What could be improved

Question 8

What are the different scrum roles?

Answer 8

• Product Owner
  
  • Rep the customer
  • Develops product backlog
  • Owns what to develop and why
• Scrum master
  
  • Person that manages the sprint and the process
  • Ensures people follow the sprint
• Dev team
  
  • Designers, programmers, tested and data scientist
  • Self organising no heirachy
  • Doesnt question what they build but rather how they will build it