GoConqr has a new look! Let us know what you think.

Sign up free

Quiz

agile

Marty Collins 13 questions

Take the quiz

This quiz has question types that open in the usual player.

Questions in this quiz (13)

  1. 1Waterfall Method

    Each step must be [blank_start]completed[blank_end] before moving on to the next

    All steps must be completed before any [blank_start]value[blank_end] is delivered to the customer

    Lends itself to scheduling and [blank_start]reporting[blank_end]

    Clings to idea of Big [blank_start]Design[blank_end] Up Front (BDUF)…perfecting the design before moving on to implementation

    Perfection of this sort is better suited to other forms of engineering, not [blank_start]software[blank_end] engineering
    Image for question 1
    1. Acompleted
    2. Bvalue
    3. Creporting
    4. DDesign
    5. Esoftware
  2. 2Agile ManifestoImage for question 2
    1. Aprocesses and tools
    2. Bcomprehensive documentation
    3. Ccontract negotiation
    4. Dfollowing a plan
  3. 3Agile is Good

    Agile is a [blank_start]value[blank_end] system
    Agile does not dictate any one [blank_start]approach[blank_end]
    Agile has worked well for many [blank_start]projects[blank_end]

    1. Avalue
    2. Bapproach
    3. Cprojects
  4. 4Kanban

    Kanban is an approach to software development based on the principles of [blank_start]Lean[blank_end]
    1. ALean
  5. 5The Board

    One possible solution is to be able to see the [blank_start]work[blank_end] items all of the time

    For every [blank_start]item[blank_end] a team is working on create a little [blank_start]note[blank_end] and put it on the wall

    1. Awork
    2. Bitem
    3. Cnote
  6. 6Work in Process (WIP)

    WIP is the number of work items you have going at the [blank_start]same[blank_end] time (the stickies on the board)

    Less WIP leads to quicker flow through your process: shorter [blank_start]lead[blank_end] times

    You become more [blank_start]Agile[blank_end] because you deliver the important stuff first

    In the first iteration there was a lot of waiting but each worker was [blank_start]efficient[blank_end] and worked through the entire batch before handing it down

    In the last iteration every worker worked for a longer time making them less efficient as individuals but more efficient as a team

    So…optimising your process for quicker flow can lead to poorer [blank_start]resource[blank_end] [blank_start]utilisation[blank_end]
    1. Asame
    2. Blead
    3. CAgile
    4. Defficient
    5. Eresource
    6. Futilisation
  7. 7Limit Work in Process (WIP)

    Strive to work with fewer [blank_start]items[blank_end] at the same time

    Smaller [blank_start]batches[blank_end] means shorter lead times

    Resource efficiency [blank_start]decreases[blank_end] while flow efficiency [blank_start]increases[blank_end]

    Rather than starting a new work item (thereby increasing the batch…creating a new sticky) help someone in the [blank_start]team[blank_end] finish one already in progress

    Use [blank_start]visualisation[blank_end] to make the limits explicit
    1. Aitems
    2. Bbatches
    3. Cdecreases
    4. Dincreases
    5. Eteam
    6. Fvisualisation
  8. 8Use visualisation to make the limits explicit

    Choose a [blank_start]maximum[blank_end] number of work items allowed to be in progress at the same time

    When value starts to be delivered to the customer there will be less demand for [blank_start]estimates[blank_end]

    You won’t feel [blank_start]swamped[blank_end] with work because you have a limit on how many things you work on at the same time

    If someone adds a [blank_start]new[blank_end] item they will have to decide what gets taken out
    1. Amaximum
    2. Bestimates
    3. Cswamped
    4. Dnew
  9. 9How low should the limit be?

    Low WIP limit creates a lot of [blank_start]slack[blank_end]. Think of one work item..as soon as it is ready for development the developers could pick it up and start working on it…as soon as it is ready for testing the testers could pick it up and start working on it etc

    Good for [blank_start]lead[blank_end] times but companies will not pay for people to sit [blank_start]idle[blank_end]

    You need a balance…Fast Flow Vs Work to do …the WIP limit is a trigger for discussion
    1. Aslack
    2. Blead
    3. Cidle
  10. 10Queues

    Note the WIP limit as an integer in the column

    Introducing queues will allow you to [blank_start]visualise[blank_end] what is waiting and what is in progress
    Have queues where there is a limited [blank_start]resource[blank_end]…it’s a good way of signalling that work is ready to be pulled to the next stage

    You can manipulate the WIP limit by [blank_start]reallocating[blank_end] resources
    Image for question 10
    1. Avisualise
    2. Bresource
    3. Creallocating

Information

Description
Quiz on agile, created by Marty Collins on 23/04/2016.
Language
English
Views
12
Rating
No ratings yet
Rate this quiz
Rate this quiz

Feedback

What is it about?

What do you think of the new look?

How do you like it?