Agile & DevOps
21 important questions on Agile & DevOps
What is the starting point of agile development methods?
What are the three principles of XP?
- Feedback
- Simplicity
- Embrace change
What are the four basic activities of XP?
- Coding
- Testing
- Listening
- Designing
- Higher grades + faster learning
- Never study anything twice
- 100% sure, 100% understanding
What is an important element of test-driven development?
What are some main points to summarize scrum?
- Split a project into brief manageable 'sprints' (time box)
- Utilize teams better; feedback and hand-over in the team
- Development and test before delivery
- Handle changes in requirements
What roles are there within Scrum?
- Scrum master: organizes the work, budget, etc, facilitator; buffer
- Product owner: ensures crucial features are included; prioritizes
- Development team: autonomous; deliver quality specialists; generalists
How are the Scrum roles different of traditional project management?
The team is autonomous, allowed to make decisions and that also means that managers learn to let go.
The representatives of the business are but in the team and called the product owner.
What are the Scrum rituals?
- Sprint: time-boxed effort (2-4 weeks); facilitated by scrum master
- Planning: (max 4 hours for a 2-week sprint)
- communicate goals, select backlog items, prepare (decompose task)
- Daily Scrum (max 15 min)
- what did I do? what will I do? any impediments?
- Review and retrospective (2 hours)
- review work that was completed and not completed, and present to stakeholders (demo)
- retrospective: reflect on sprint, and agree on improvements
Which Scrum rituals were later added by people?
- Backlog refinement: reviewing priorities of backlog items
- Scrum of Scrums: coordinate multiple teams on the same product
What are the Scrum artifacts?
- Product backlog: items to work on: ordered list of requirements
- Sprint backlog: work for development team in the next sprint
- Product Increment: sum of completed product backlog items in a sprint
Product backlog items are often written in the form of stories? Why is this so useful?
What are the management tools used with Scrum?
- Planning poker
- estimate amount of work (using team expertise)
- Sprint burn-down chart:
- shows remaining work in sprint backlog
- updated in daily scrum
- Release burn-up chart:
- shows progress towards scheduled release
- Discussion:
- key performance indicators for a Scrum team?
Why does Scrum work?
- Handle change, uncertainty: add user stories, prioritize; review and retrospective
- Handle complexity: decomposition in sprints, good teams
- Time gains: only do important stuff; communication; focus on one project
What if we need 12 teams running in parallel? How to coordinate the teams and along them with business objectives?
- SAFE-framework
- LeSS-framework
- Spotify model
What are the main four principles of agile project management?
- Minimum critical specification: no more should be specified than is absolutely essential to overall success (decided by team)
- Autonomous teams: autonomous teams are responsible for managing and monitoring their processes and executing tasks (rest of the organization accepts these decisions)
- Redundancy: team members are skilled in more than one function
- Feedback and learning: integral to project execution and interaction with the environment (to deal with ‘wicked problems’ - don’t have a fixed solution )
Is quality control wastage?
Is compliance with rules and regulations wastage?
What are the five essential steps in Lean?
- Identify which features create value; rest is considered wastage.
- Identify the sequence of activities called the value stream.
- Make the activities flow.
- Let the customer pull product or service through the process (work only when there is demand for it)
- Perfect the process.
IT auditors traditionally demand DTAP practices. Which two things does this imply?
- Formal roles in deployment process (segregation of duties)
- Develop | Test | Acceptance | Production
- e.g. ITIL change management / release management:
- all changes must first be approved by CAB (Change Advisory Board)
- all changed must have been tested, and accepted by business
- Environment (e.g. separate SAP servers) to support these stages.
- DTAP-street; facilitating strict procedures
Originally the DTAP practices were a barrier to DevOps. Why?
Not all change is good. How do you deal with stability? How do you deal with things that need to remain stable in order to make sure that future projects also fit?
The question on the page originate from the summary of the following study material:
- A unique study and practice tool
- Never study anything twice again
- Get the grades you hope for
- 100% sure, 100% understanding