Scrum Basics Flashcards

1
Q

What is the Agile Mindset?

A

Agile Mindset: is the way of thinking and acting according to Agile values and principles.

Being Agile means that you have the agile mindset instead of just following practices outlined by some framework without understanding the reason behind these practices.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is Agile?

A

Agile: is a particular mindset that is based on a well-defined set of values and principles.

Try to understand the values and principles and live them.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is the Agile Manifesto?

A

Agile Manifesto: is a document written in 2001 by seventeen independent-minded software practicioners, known as “The Agile Alliance”, that identifies 4 core values and 12 principles.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are Agile Practices?

A

Agile Practices: are the various activities and processes used by an Agile team to apply the Agile mindset to their workload. The most common Agile practices are: backlog preparation & refinement, review events, retrospectives etc…

Implementing only the practices without the mindset is Doing Agile without Being Agile. And it leads to frustration.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are the 4 Agile Values?

A
  1. Individuals & Interactions - over - Processes & Tools
  2. Working Software - over - Comprehensive Documentation
  3. Customer Collaboration - over - Contract Negotiation
  4. Responding to Change - over - Following a Plan
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are the first six Agile Principles?

A
  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  4. Business people and developers must work together daily throughout the project.
  5. Build projects around motiviated individuals. Give them the environment and support they need, and trust them to get the job done.
  6. The most efficient and effective method of conveying information to and within a developtment team is face-to-face conversation.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the next six Agile Principles?

A
  1. Working software is the primary measure of progress
  2. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  3. Continuous attention to technical excellence and good design enhances agility.
  4. Simplicity - the art of maximizing the amount of work not done - is essential
  5. The best architectures, requirements, and designs emerge from self-organizing teams.
  6. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is an adaptive approach in project management?

A

Also called change-driven approach. It adapts to the project’s changing environment. This is suitable for projects with high levels of uncertainty and volatility, and in which requirements are likely to change throughout the project. This involves frequent planning and can be iterative, incremental or both as in agile.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is a predictive approach in project management?

A

Also called plan-driven or waterfall. It’s the traditional work management approach, where the scope, time, cost, requirements, and acceptance criteria are planned and determined upfront before starting work execution. This approach is sequential and rigid, with a single delivery and predefined overlapping phases.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Explain the iterative approach.

A

It implies a high-level scope definition at the beginning of the project while progressively developing the cost and schedule through timeboxed iterations as requirements become clearer until the final product is fully developed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Explain the incremental approach.

A

It delivers ready-to-use product functionalities to the customer at the end of each iteration. These partial outcomes are known as increments, which present functional, tested, demonstrated, and accepted subsets of the final deliverable.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What Roles do you have in Scrum?

A
  • Product Owner (Represents the customer, shares the vision, manages the product backlog)
  • Scrum Master (Supports the team, maintains the scrum process, removes impediments)
  • Development Team (Delivers the increment, is self-organized, is cross-functional)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What Events do you have in Scrum?

A
  • The Sprint
  • Sprint Planning
  • Daily Scrum
  • Sprint Review
  • Sprint Retrospective
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What Artifacts do you have in Scrum?

A
  • Product Backlog
  • Sprint Backlog
  • Increment
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What “Best Practices” do you have in Scrum?

A
  • User Stories
  • Poker Planning
  • Scrum Board
  • Backlog Refinement
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the three pillars of empiricism in Scrum?

A

Scrum is based on Empiricism. This means knowledge comes from experience and decision-making is based on what is observed.

Transparency: Work is visible to those doing and receiving it.
Inspection: Progress towards goals is frequently inspected.
Adaptation: Deviation is addressed ASAP through rapid adjustment

17
Q

What is the broad definition of a Product Owner, also compare it to a Product Manager.

A

The Product Owner serves as a SPOC (Single Point of Contact) between the stakeholder and the the development team, facilitating communication and guiding the product’s development according to the defined vision and roadmap.

Skills:
Business skills are:
- Ability to imagine and pursue innovative ideas (visionary)
- A deep understang of the industry
- Ability to adapt to changes, flexible mindset

Technical skills are:
- Confident to make decisions about the product
- Ability to discuss with developers and understand their choices

People skills are:
- Excellent communication skills
- Ability to motivate people
- Ability to build good relationships with stakeholders
- Ability to collaborate with the Scrum Master and Development team

PO vs. PM
Large companies tend to have more than one Product Owner. In this case, a Product Manager, aka Chief Product Owner, takes the responsibility of aligning all product owners with the overall strategy.

18
Q

What are the responsibilities of a Product Owner?

A

Product Discovery
- Product Discovery is an ongoing process, involving continuous assessment and adaptation based on the evolving requirements of the customer.
- The product owner (PO) discusses the product strategy with the customer and shares it with the stakeholders and the development team.
- The PO performs interviews with potential users, meets with stakeholders, hosts workshops with current users, etc. to collect or refine requirement.
- The PO listens to the users’ pain points to identify opportunities for improving the product.

Product Implementation
- Throughout implementation, the PO should be available to respond to the Development team’s questions and concerns.
- The PO maintains the product backlog by continuously refining and prioritizing its items.
- The PO collaborates with the Development team to define and implement the product releases.
- The PO participates in the sprint planning events by defining sprint goals, top priorities, and acceptance criteria.
- The PO evaluates the work done by the Development team and provides feedback during the sprint review events.

19
Q

What is the broad definition of a Scrum Master?

A

The Scrum Master is responsible for facilitating the Scrum process and ensuring that the Scrum team adheres to its principles and practices.

They serve as a servant-leader, coaching the team on the Agile mindset, removing impediments to progress, and fostering a collaborative and self-organizing environment.

Skills:
Soft Skills:
- Has the ability to build good relationships with the development team
- Employ emotional intelligence to build trust and confidence
- Active listening and support to the development team

Technical Skills:
- Very knowledgeable about Agile Mindset and Scrum Practices.
- Has the ability to coach the Development Team

Scrum Master vs. Project Manager
While both roles consist of managing projects, the Scrum Master focuses on facilitating the Scrum process and empowering the team, while the traditional Project Manager follows a more structured approach with detailed planning and direct oversight of the project.

In Scrum, most of the responsibilities traditionally held by a Product Manager are divided between the Scrum Master (Facilitator, Mentor, Servant Leader) and the Product Owner (Decision Maker, Controller, Situational Leader).

20
Q

What does Servant Leadership mean to you?

A

It is a leadership style where the leader’s primary focus is on serving and empowering their team members.

The leader strives to create a supportive and collaborative environment where development team members feel valued and motivated.

  • Encouraging the team to improve their skills and performance
  • Removing any impediments the team might face
  • Prompting well-being within the project
21
Q

What are the main Responsibilites of a Scrum Master?

A

Scrum Champion
The Scrum Master helps the Scrum team and the organization follow Agile values and Scrum practices.

Empower the Team
The Scrum Master empowers the team to make decisions collectively and take ownership of their work.

Mediating Conflicts
In cases of disagreement, the Scrum Master acts as a neutral mediator, helping the team find common ground.

Encourage Openness
The Scrum Master fosters an environment where team members feel comfortable expressing their ideas, concerns and opinions.

Encourage Learning
The Scrum Master fosters a culture of continous learning to help the team enhance their competencies and performance.

Facilitate Consensus
The Scrum Master facilitates collaborative discussions by ensuring that all voices are heard and considered.

Protect the Team
The Scrum Master helps the team stay focused by shielding them from external distractions.

Remove Impediments
The Scrum Master protects the Dev team from progress impediments, both reactively and proactively

22
Q

What is a cross-functional team?

A

A cross-functional team is made of members with diverse substantial skill sets, making it possible to produce the project deliverables with no external dependency. The team is fully capable to develop the product from Analysis to Production. That means the team has BA’s, Developers, UX-designers, testers and integrators.

Having to throw a partially finished product to another team for whatever reason, creates queues, delays, technical debt, no understanding and lacking a feeling of responsibility.

23
Q

What are T-shaped and I-shaped team members?

A

A T-shaped team member is a generalizing specialist who has one or multiple skills with deep expertise in a particular field while other skills tend to be rather on a basic level. T-shaped people are usually more willing to collaborate.

An I-shaped team member has deep specialization and expertise in one domain and has no or little interest in participating or getting involved in work outside of that domain.

24
Q

What does baselining mean? How is it important for you personally and how for the team?

A

Baselining helps you to describe the status quo, before you committ to an intervention. After the intervention you can check if the intervention was successfull. It can be a personal intervention or it can be an agile experiment.

  1. Pre-Training assessment: represents a baseline of where the team stands before receiving the intended training.
  2. Mid-Training assessment: is optional, but it allows to make any adjustments if needed.
  3. Post-Training assessment: reveals the efficiency of the training by comparing its results to the pre-training one.
25
What is Outcome versus Output?
**Outcome:** the reason for creating the product in the first place. It aims to address user pain points and deliver valuable gains. Outcomes are often intangible, making them hard to measure, why you often lack KPI's that measure exactly that. **Output:** project activities or work items that are performed in order to achieve outcomes. Outputs are easily measurable since they often represent tangible results. completing project activities means creating outputs but does not necessarily mean that project outcomes were also achieved or if the created outputs are really valuable. Since it's so easy to measure output, many KPI's include them althoug that is rarely useful. E.g. lines of code written, or commits, or even features. If you build 10 features each sprint but they create x5 times as many bugs, it's clearly no use the measure performance like that.
26
What is value stream mapping?
A lean technique for visualizing and measuring value-adding activities versus non-value-adding activities. It helps to create value by identifying and removing waste from the existing process, system, or product. E.g. you in the airport Find your check-in Counter (3') wait (15') Check-In (2') wait (20') Security gate (10') wait (10') Find your boarding gate (10') wait (40') board the plane (1') wait(5') you in the plane (4') **Total Cycle Time** = Value Add Time + non Value Add Time = 120' **Process Cycle Efficiency** = Total Value Add Time / Total Cycle Time = 25%
27
What are the 5 Scrum values?
Scrum is more about behavior than it is about process. Values drive behavior. The framework of Scrum is based upon five core values: - Commitment - Focus - Openness - Respect - Courage In the context of Scrum, our decisions, the steps we take, the way we play the game, the practices we include and the activities we undertake within Scrum should all re-enforce these values, not diminish or undermine them, whether it concerns the "process" or the "people" aspects of Scrum
28
Explain the first Scrum Value: Commitment
Commitment is about engagement and dedication and applies to the actions and the intensity of the effort. It is not about the final result, as this in itself is often uncertain and unpredictable for complex challenges in complex circumstances. In the complex, creative and highly unpredictable worlds that Scrum helps us to navigate, a promise to deliver exact, in the sense of precisely predicted, output or scope against time and budget is simply not possible, not even for a Sprint. Too many of the variables that influence the work are unknown or behave in unpredictable ways, even within a Sprint.
29
Explain the second Scrum Value: Focus
The time-boxing of Scrum encourages the players to focus on what's most important now without being bothered by considerations of what might stand a chance of becoming important at some unknown point in the future. They focus on the work needed to get things done. They focus on the simplest thing that might possibly work. The Sprint Goal gives focus to a period of two to four weeks. Within that period, the Daily Scrum helps people collaboratively focus on the immediate daily work needed to make the best possible progress towards the Sprint Goal. A Product Goal provides direction and focus across multiple Sprints and helps in finding and keeping direction
30
Explain the third Scrum Value: Openness
The empiricism and self-organization of Scrum require transparency, openness and honesty. The players want to check on the real situation in order to make sensible adaptations. The players are open about their work, progress, learnings and problems. But they are also open for the people aspect of work and what working with people involves. The players are open to collaborate across disciplines, skills, functions and job descriptions without external procedures or rules of governance dictating that. They are open to collaborate with stakeholders and the wider environment.
31
Explain the fourth Scrum Value: Respect
The broader Scrum ecosystem thrives on respect for people, their professional experience and their personal background. The players respect and strive for diversity. They respect different opinions and each other's skills, expertise and insights. Differences in opinions are respectfully dealt with in a state of productive dissent. They respect the fact that customers change their mind. They show respect for the sponsors of their initiatives by not building or keeping functions that are never used and that increase the total cost of the product. They show respect by not wasting money on things that are not valuable. They show respect for the users by fixing their problems.
32
Explain the fifth Scrum Value: Courage
The players show courage by not building stuff that nobody wants. Courage in admitting that requirements will never be perfect and that no plan can capture reality and complexity. They show the courage to welcome change and different opinions as a source of inspiration and innovation. Courage to not deliver undone versions of product. Courage in sharing all possible information that might help the team and the organization. Courage in entering a state of productive dissent. Courage in admitting that nobody is perfect. Courage to change direction. Courage to share risks and benefits. Courage to let go of the illusory certainties of the past.