Agile & DevOps

21 important questions on Agile & DevOps

What is the starting point of agile development methods?

The starting point of agile development methods is that you see software development nog longer as a technical problem, but rather as a social process. You focus on the team, the programmers and namely, the people.

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
Discover Study Smart

What is an important element of test-driven development?

Versioning: delivery pipeline with very strict stages for different versions of software and in particular part of that is that you can only move something to the 'done' phase when it passes the test.

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?

There is no project manager, but a scrum master. This is the facilitator, who needs to surf the team. Team is considered more important than the manager, should pave the way and take all the difficulties away from the team (like budget).

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?

Artefacts are the ways of recording process. The product owner is key because they prioritize the product backlog items.
  • 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?

Because it describes what will be delivered and doesn't have to focus on how it will be delivered. Moreover, it is a useful way of enabling communication between end-users and developers.

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?


  1. Minimum critical specification: no more should be specified than is absolutely essential to overall success (decided by team)
  2. Autonomous teams: autonomous teams are responsible for managing and monitoring their processes and executing tasks (rest of the organization accepts these decisions)
  3. Redundancy: team members are skilled in more than one function
  4. 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?

If the quality control is added on top if it, then in a sense you are doing work that the engineering should bedding themselves

Is compliance with rules and regulations wastage?

Compliance is a part of quality so we have to build it into the process and procedure. Sometimes it is called 'compliance by design'. Without compliance the product would have no value for the customer

What are the five essential steps in Lean?

  1. Identify which features create value; rest is considered wastage.
  2. Identify the sequence of activities called the value stream.
  3. Make the activities flow.
  4. Let the customer pull product or service through the process  (work only when there is  demand for it)
  5. 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?

DevOps we have mixed teams with people from production and development joining, but here there is a clear segregation of duties between development and production. So how can that be solved? Not completely, some differences remain. One of the solutions is that in modern environments a lot of the ideas behind DTAP are now being enforced by the environment and that actually DevOps itself can take it into account.

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?

That can only be done if you stick to standard, which needs to be build in in the procedures. Asset management, you don’t want to waste resources on a particular course going ‘left’ and then later decide that you want to go right. In general governance, are all responsibilities. How do you interact between specialized teams, and where are the interdependencies between decision making. Sometimes if decision are taken lower in the organization, it has an impact at other levels too and this needs to be aligned.

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
Remember faster, study better. Scientifically proven.
Trustpilot Logo