That the limit has not been surpassed , as the limit is 3
That there are 3 tasks when the limit is a maximum of 2, but this should be an exceptional situation
It's not possible that this happens as the limit is 2 and no more than 2 cards could be managed at the same time.
Question 2
Question
A [blank_start]column[blank_end] is the status of the card being managed, which is tied to certain policies to be moved to the next [blank_start]column[blank_end].
A [blank_start]lane[blank_end] is a way to differentiate the cards in different groups or projects.
Answer
column
column
lane
Question 3
Question
A task that is under investigation by Development should be under the column [blank_start]SOLVING[blank_end]
A task that needs more info should be under the column [blank_start]REQUESTED[blank_end]
A task should always be created in the [blank_start]BACKLOG[blank_end] area
The In Progress Column consists of [blank_start]INVESTIGATING[blank_end] SOLVING AND WAITING TO BE SOLVED
Only a tasks that has a Solving Reason should be moved to [blank_start]Closed[blank_end]
Answer
SOLVING
REQUESTED
WAITING TO BE SOLVED
BACKLOG
INVESTIGATING
Closed
RESOLVING
Question 4
Question
We consider a task info is completed by EuroMIS when AT LEAST the following are fullfiled...
Answer
Service Level
Priority
Size
PBI
Deadline
Environment
Solving Reason
External Link
Agent
Repro Rate
Question 5
Question
The FIFO rule means....
Answer
We should have everything in the Backlog, save some time and start working every single card at the same time
We should work with 1 element, develop and finish it before starting with other.
FIrst Information, First Out, the first task that has information is the first one we should work with
First In Fx Online, FxOnline should always be the Priority
Question 6
Question
If the limit of a column is surpassed, we should think of action the tasks in the overflown column before taking other tasks
Answer
True
False
Question 7
Question
Items in the column [blank_start]REQUESTED[blank_end] are being assessed to verify all the information is present.
ENTRY Policy: Items MUST be reproducible, have a T Shirt size, priority and class of service assigned.
EXIT Policy: All the information required is fulfilled.
Buffer column [blank_start]WAITING TO BE SOLVED[blank_end] when Solving's WIP is full
EXIT Policy: Solving WIP allows more Items
Items in the column [blank_start]CLOSED[blank_end] are being closed as the outcome is provided
EXIT Policy:
Submitter has acknowledged the receipt of the communication and agrees on the outcome
EuroMIS has been informed on the communication of the outcome
Items in the column [blank_start]INVESTIGATING[blank_end] are being investigated to determine if QA/DEV are to work in them or can be closed.
EXIT Policy:
We are sure it's a QA problem and the problem hasn't been solved yet. = Solving
We are sure it's a DEV problem that hasn't been solved yet = Closed
We are sure it's not a QA/DEV problem AND the requester agrees on the outcome = Closed
Items in the column [blank_start]SOLVING[blank_end] are being solved with a defined outcome
EXIT Policy
We are sure it's a QA problem and the outcome has been transmitted and agreed with the requester
We are sure it's a DEV problem, a bug is created in TFS or a SCR has been created.
SOLVING REASON custom field has been fullfiled