Reference no: EM133200714

Question 1

Evaluate the Kanban board below. Consider the visualization flow of work, level of detail, missing columns, definition of done, and acceptance criteria etc.

• Identify a minimum of two issues with the current board, explain why they are issues, and alter them to make a more effective board. For example, an issue could be related to the workflow and life cycle of user stories, and placement in the board and level of granularity/consistency, a missing column etc.
• Define done for each column.
• List any assumptions or constraints relevant to your responses.  

Backlog	Done	Req	Dev
Feature 1		User story 1
User story 2	User story 2	Epic 2
User story 3

Question 2

Translate the statement below to a user story.

"The scorekeeper is asking us to automatically calculate the aggregate of goals and misses of the players. She doesn't want to have to manually do the math to determine the total number of goals and misses for each game. Knowing the aggregate score by game will allow the scorekeeper to accurately declare the winner".

Question 3

Convert below user stories into an epic:

As a release manager, I want my releases mapped to different sprints so I can easily track them.

As a system administrator, I want to be granted appropriate rights so the access levels are accurate.

As a user, I want to be able to re-order cards so I can better represent their priority and ensure the board is accurate.

Answer (on the lines of):

As an agilist, I want to manage my backlog easily.

Question 4

Utilizing the following table, complete the table by prioritizing the following features and assigning them a rank (rank 1 is highest priority). Accompanying your table, your response should include a brief report that highlights the following:

• The name of the prioritization technique applied and why you chose to implement it.
• The list of factors considered in your prioritization and why they are important.
• Any assumptions and constraints in your prioritization  

Feature	Value to Customer	Effort	Priority
F1	21	300
F2	320	320
F3	390	3
F4	14	4

Note: a higher score represents higher value or effort.

Reference:

International Institute of Business Analysis. (2017). Agile Extension to the BABOK® Guide: V2. Oakville, ON: International Institute of Business Analysis.