Unit 3-Lecture-2-3

Agile Development and
Devops
Unit 3 Lecture 2
Scrum Scaling
• When should you scale Scrum to multiple teams? This question isn’t as difficult as it may sound. Scrum is based on the
delivery of a product. The optimal development team size is between 3 and 9 people plus the product owner and Scrum
Master. This means that if you can deliver your product with a team of 9 people or less, then there is no need to scale.
Distributed Scrum Practices:
• Meeting face-to-face is the only way to build trust
• Establish a shared project vision
• Establish continuous integration (CI) with high test coverage across all teams
• Establish a synchronization and communication plan
• Use short sprints
• ScrumMaster at both locations
• Execute 3-4 sprints with entire team at local site
• Involve full team in release planning, iteration planning, review, and retrospectives.
• Agile Environments and tools
• An agile environment is defined as an environment that creates and supports a culture that
encourages a team of people to work toward a common goal. This is done by incorporating the
importance and value of individuals and their interactions - especially in terms of working to
achieve quality, collaboration, and acceptance of frequent change in the company culture.
The 10 Characteristics of an Agile Environment

• 1. Leadership is first and foremost about purpose
• 2. Business value is delivered by small, co-located, cross-functional and self-organizing teams
• 3. Team membership is stable over a longer period to increase performance
• 4. Management empowers decentralized decision-making
• 5. Temporary documentation is replaced with face-to-face interaction
• 6. Full transparency instills trust
• 7. Big projects are delivered as a series of small independent projects all adding value
• 8. Frequent deliveries means short feedback loops which lead to higher quality and engagement
• 9. Relationships and results brings joy of work (and happier people produce more!)
• 10. Make continuous improvement a natural part of the company culture (failure needs to be an option )
Kanban
• Kanban is a popular framework used to implement agile and DevOps software development. It requires real-
time communication of capacity and full transparency of work. Work items are represented visually on a
kanban board, allowing team members to see the state of every piece of work at any time .
• Kanban is a scheduling system for lean manufacturing and just-in-time manufacturing.
Scrum Kanban
Scrum vs Kanban
Scrum stresses on planning. It starts with sprint planning and ends up Kanban is open to making changes on the go. It means there is less
with sprint retrospective.There are many meetings held which help to rigidity and things can change frequently.
assure that the team is aligned with the next steps, priorities, and
learnings from previous sprints.
It recommends collection of time measurements made during sprints Kanban recommends graphs to get an overview of team's progress over
time.
Scrum no longer asks for a commitment from teams. Instead, it is about Kanban relies on time-boxing and forecasts.
the sprint goals and forecasts.
It stresses on planning, and so estimation has a very important role in Kanban has no mandatory requirements for estimation.
Scrum
Every individual has their role and responsibilities. No set roles so flexibility in term of individual responsibilities.
The iterations/Sprints are fixed in duration. This duration varies from 2 Kanban is not based on duration. This thing is measured regarding Cycle
weeks to 1 month. times.
Xtreme Programming vs Scrum
Scrum Extreme Programming (XP)
In Scrum framework, team work in iterations In Extreme Programming(XP), teamwork for 1-2
called Sprint which are 1-2 month long. weeks only.
Scrum model do not allow changes in their timeline Extreme Programming allow changes in their set
or their guidelines. timelines.
Extreme Programming emphasizes strong

Scrum emphasizes self-organization.
engineering practices
In Scrum framework, team determines the In Extreme Programming, team have to follow a
sequence in which the product will be developed. strict priority order or pre-determined priority order.
Scrum framework is not fully described. If you want

Extreme Programming(XP) can be directly applied
to adopt it then you need to fill the framework with
to a team. Extreme Programming is also known for
your own frameworks method like XP, DSDM or
its Ready-to-apply features.
Kanban.

Unit 3-Lecture-2-3

Uploaded by

Copyright:

Available Formats

Unit 3-Lecture-2-3

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Unit 3-Lecture-2-3

Uploaded by

Copyright:

Available Formats

Agile Development and

The 10 Characteristics of an Agile Environment

Scrum Extreme Programming (XP)

Extreme Programming emphasizes strong

Scrum framework is not fully described. If you want

You might also like