MOC EXAM 25Q Agile 76% 75->100

Question 1

The scrum master on your Agile project has asked you for the total lead time of a particular feature. You add up the cycle time of all the cards that contributed to that feature. What other two factors must you take into consideration when calculating total lead time?

• Time for testing the code and time for merging the code.
• Meeting times and lunch times
• Value-added time and non-value added time
• Testing and documenting

Answer 1

> Lead time is a concept from Lean and the Toyota Production System.

Whenever you are calculating Cycle time (smaller items such as processes, story cards, or an iteration in a larger project) or Lead time (larger items such as features or the project itself) you must take into consideration both : value-added time (that directly contributes to the customer outcome) and non-value-added time (that does not directly contribute to the customer outcome).

Question 2

The twelve Agile clarifying principles also match up with the best advice for keeping things simple in a project. Which of the below is a correct Agile clarifying principle?

• Simplicity is only possible when the team first understands how complex the system is.
• Simplicity is part of every project, everyone naturally simplifies the work as part of their role.
• Simplicity reduces cost in a project, ensuring executives are always simplifying the process and the system.
• Simplicity – the art of maximising the amount of work not done – is essential.

Answer 2

The correct answer here is “Simplicity – the art of maximising the amount of work not done – is essential” being an Agile clarifying principle.

Question 3

You are the product owner in an Agile team, working with the developers to create Story Cards to place in the product backlog. In the three C’s of user story creation, what will you do first?

• Create the card, which is the physical (or software driven) media describing a user story.
• Confirm the acceptance criteria to go into the user story.
• Have a Conversation with the team to flesh out the requirements and criteria.
• Catch defects before they are developed by working with Quality testers before and after.

Answer 3

The three C’s of User Story Creation include:
Creating the card,
Conversation with the Product owner and developers to explain how the software or design will be used, and
Confirming the acceptance criteria and the definition of done.

Question 4

You are working on the product backlog with your Agile project team, and creating user stories to be prioritised. Which of the below is the best answer for what should go into a user story card?

• Key risks of the project and the feature being delivered, with their owners and mitigations.
• A wireframe of the feature to be developed that developers can work with.
• The requirement, its criticality, expected development and test duration, and the acceptance criteria for that story.
• The benefit of the feature so key stakeholders are aware of what they will get.

Answer 4

Agile story cards should have:
- the requirement,
- its criticality,
- test details and
- clear acceptance criteria.

Question 5

You are an Agile project manager and have begun creating user stories with your Agile project team to go into the product backlog. You have created the card, added requirements, criticality and acceptance criteria. What will you do next?

• Place the card on the Kanban board so the team can clearly see the future work.
• Have a conversation with developers about how the software will be used, confirm the acceptance criteria and definition of done.
• Prioritise the card in the upcoming sprint backlog to ensure the work gets done.
• Advise the project sponsor and risk manager of the feature details to ensure risks are captured.

Answer 5

The three C’s on user story creation are: Card, Conversation and Confirmation. Once the user story card is created, have a conversation with developers and testers to ensure understanding, check for any gaps, and estimate the effort required. Finally, confirm the acceptance criteria. You can then place it in the backlog for prioritisation in an upcoming sprint.

Question 6

You are working on a project as an Agile Project Manager. The executive manager who will own the product you are delivering would like to focus primarily on set processes and tools to manage to project. What will you recommend to them instead?

• Focus on the definition of success as defined by the project manager
• Focus primarily on the individuals and interactions involved
• Focus primarily on the scope of the project
• Focus primarily on the people involved in the project

Answer 6

The Agile manifesto recommends focusing on Individuals and Interactions over processes and tools.
Projects are run by people, products are developed by people for people to use, and our interactions either make or break a project.

Question 7

You are running an Agile project and meet with the team for the next sprint planning meeting. What will you do next?

• Negotiate the scope and costs of the project with the project sponsor.
• Walk through three questions with the team—What did I do yesterday? What will I do today? Is anything blocking me?
• The development team demonstrates the working feature to the product owner, who marks it as complete.
• The product owner shares the updated backlog, and the team discusses it to ensure a shared understanding.

Answer 7

The product owner should “share” the updated items in the product backlog with the team and ensure a shared understanding “before” moving forward.