Exam Flashcards
Describe the meaning of “Make the build self testing” as it relates to continuous integration
- Need a suite of automated tests which check a large part of the code base
- Failure of a test should cause the build to fail
Agile 10 Principles are:
First 5
- Active user involvement
- Team is empowered to make decisions
- Requirements evolve, timeline is fixed
- Requirements = high level, lightweight, visual
- small incremental releases, then iterate
Agile practices are:
Daily Meeting Iterative & incremental (timeboxing, requirements freeze) Planning Game / Planning Poker CI, TDD, BDD, Sprint Review Reflections, Retrospectives etc
Kanban vs Scrum - 10 marks
Same/Different
Consequences of the differences
Kanban is about limiting work in progress to reduce cycle time, to find and eliminate bottlenecks, while providing the ability to expedite a feature. Scrum focusses on providing value in a set time frame, may not deal with bottle necks, can’t be changed in a sprint and has direct user involvement before & after each sprint
CI Tools - name & describe (2 marks)
Travis CI:
watches a branch and notices when there’s been an integration, then runs all the tests again.
Agile 10 Principles are:
Back 5
- Frequent delivery of products
- Complete each feature before moving on
- Apply 80/20 rule
- Test early and often (tests integrated throughout SDLR)
- collaborative & cooperative approach
Explain the Agile Principle: “Apply the 80/20 Rule”
Focus on the important 20% of effort which will generate 80% of the results
The kanban dream is to avoid: (x4)
- Building features no one needs right now
- Writing more specs than can be coded
- Writing more code than can be tested
- Testing more code than can be deployed
Kanban limits Rule of thumb:
How many cards on the board?
Add up all the team members (incl. test, BA, i/face)
DIVIDE by 2
Kanban limits Rule of thumb:
Divide by?
In the To Do column, divide total WINP/2
In any other column divide how many can work on it/2
Kanban summary (x3)
Measure Cycle Time,
Limit WINP
Make workflow visible
Scrum Summary
- Split work (user stories)
- Split time (short iterations)
- Optimise Release plan (priorities)
- Optimise Process (retrospective)
Differences between Kanban & Scrum (x6)
KB = no timebox = continuous flow KB = MMF/user cards = larger than user story KB = work is pulled = no effort estimates KB = Performance measured in CT = not V BOTH = prioritise cards (MoSCoW) SCRUM = board is reset = not persistent
4 things offered by cloud & services computing
- rapid development
- large scale, distributed applications
- resource outsourcing
- IT management with service providers
Advantages of IaaS, PaaS, SaaS (x3)
- no h/w or maint costs
- S/W always updated & patches applied
- only pay for what you use