AGILE FRAMEWORK

• An agile framework incorporates continuous planning, testing, integration and other

forms of continuous development.

• It is a flexible way to manage projects, It is a set of values and principles designed to

handle projects with changing requirements and deliver value both early and
frequently in a project timelines. There are several different frameworks used to apply
agile principles

• A framework is an approach or set of techniques and guidelines used to implement

agile and uphold its values

• Agile frameworks prioritize individuals and interactions over processes and tools.

• There are many agile frameworks available, the most popular and widely utilized are:

1. Scrum: It is the oldest and popular framework, It is known as “The art of doing twice
the work in half the time

• This framework is designed to develop complicated software and products and sustain
them in the long term

• It delivers completed work at the end of each iteration during the process

2. Extreme programming(XP): It encourages quality work and apply best practices to

engineering

• It prioritize communication and teamwork as well as shared workspaces, code

refactoring and pair programming

3.Dynamic system development method(DDSM):

It focuses on every stage of the project from conception to completion, while it was
 originally designed as a development tool to address issues with rapid action
development.

4. Feature driven development(FDD):

• It mixes the benefit of agile methodologies with model driven approaches

• It has 5 stages of work including development, listing, planning, designing and
building

5. Adaptive software development(ASD):

• It focuses on end user of the product or software and aims to promote constant
communication and transparency between the customer and the development team

• It has lifecycle based around three core messages of speculate, collaborate and learn

6. The crystal method:

It offers methodologies that can adapt to teams that change in size and approach
between projects

7. Lean software development:

• It is used to complement the principles and value set in the agile manifesto

• Its principle: eliminate waste, keep learning, defer decisions, deliver fast, empower
the team, build integrity in and see the whole

8.Disciplined agile(DA):
It is designed to work with bigger staff complement. It focuses on learning, that has
people and users as its number one priority

9. Scaled Agile framework:

• It takes elements from scrum, kanban ,xp and combines with lean, agile and Develops
to create methodologies that works well for larger teams

10. Rapid Application Development:

• It discards rigorous planning in favor of prototyping, a method which heavily

influenced the concept of constant, fast iterations
 CEREMONIES

• It is the term used to iterative software development

• It allows flexibility and quicker product delivery

• These are meetings with defined lengths, frequencies and goals

• It helps teams to plan, track and engage stakeholders with their work and help them
reflect on how well they work together

• With agile ceremonies, teams in an organization can benefit from

• Enhanced ability to manage changing priorities

• Acceleration of software development

• Increase in team productivity

• Improved business and IT alignment

• Agile scrum has 5 ceremonies

• Sprint, sprint planning, Daily scrum, sprint review and sprint retrospective

• If it is managed correctly it supports high level of productivity and effective

communication and collaboration between the project team and stakeholders

SPRINT

• The projects that follow scrum delivers work in short bursts called sprints

• It takes on average 2 weeks

• It has several roles, one of them is project owner- who maintains and prioritize a list
of required project deliverables known as product backlog

• The product owner finds out the interest of stakeholder and at the beginning of each
sprint, works with project team to decide which deliverables should be tackled next

• This is the heartbeat of the scrum

SPRINT PLANNING

• Here scrum team comes together to understand to understand the prioritized

product backlog items and how they map to the product goals
• It can take up to 4 hours

• Sprint planning meetings set out precisely what the team will accomplish during the
sprint. The Product Owner is responsible for bringing company feedback and an up-
to-date and prioritized product backlog to the meeting.

DAILY SCRUM

• It occurs everyday for 15 minutes

• Here team meets and discusses about progress of their work

• The team has to answer:

• What I did yesterday

• What am I doing today

• Are there any blockers with my work

SPRINT REVIEW

• On the last day of the sprint

• Sprint review and retrospective ceremonies need to occur

• It brings scrum team, product owners, stakeholders, inspector gadget to review what
has been accomplished

• It takes upto 2 hours

SPRINT RETROSPECTIVE

• It provides better feedback on improvements for quality and effectiveness

• Once the team agrees on improvements, they should be taken up and addressed as
soon as possible

ROLES

• PRODUCT OWNER

• He represents stakeholder of the project

• He understands the requirement from stakeholder perspective and has the necessary
skills to communicate the requirements to the development team
• Responsibilities:

• Scrum backlog management

• Release management

• Stakeholder management

• SCRUM MASTER

• Ensures team coordination and supports the progress pf the project between individual
team members

• He takes the instruction from the product owner and performs accordingly

• Responsibility

• Facilitating daily scrum and sprint initiative

• Communicating between team members about requirement and planning

• Coaching team members on delivering status

• Handling administrative tasks such as conducting meetings, facilitating collaboration

and eliminating hurdles effecting project progress

• Shielding team member from external interferences and distractions

• DEVELOPMEMT TEAM MEMBERS

• The team does product development

• They perform work sprints as per the requirements provided by product owner and
coordinated by scrum master

• The required skills might be wrapped up in one or more development team members:

• Product designer

• Writer

• Programmer

• Tester

• UX specialist
 • STAKEHOLDERS

• They are not directly involved in the oproduct development process but is used to
represent a range of key roles that impact the decessions and work of the scrm team

• End user of the product

• Investors, business executives etc

• Business executives

• Production support staff etc

Additional roles for larger scrum projects

• Technical and domain expert

• An independent testing and audit team
• An integrator
• An architect owner

Overview of XP

• It is one of the most important software framework of agile model

• IT is used to improve software quality and trsponsiveness to the customer requirement

• It takes best practices that worked well in the past in program development projects

• Its goal is to allow small to mid sized team to produce high quality software and adapt
to evolving and changing requirements

Basic principles of extreme programming

• XP is based on frequent iteration through which developers implement user stories

• User stories are simple and informal statement of the customer about the
functionalities needed

• On the basis of user story team develops metaphors

• Metaphors is a vision about how the system should work

• Then the development team decide to build spike

• A spike is a program that is constructed as a solution to a problem

• Basic steps that are followed during XP are:
coding: coding includes drawing diagram that will be transformed into a code,
scripting a web based system and choosing among several laternatives

• Testing: Testing a code

• Listening: The developers need to listen to a customer properly to understand the

functionality and build a system

• Designing: Without proper design implementation would be difficult

• Feedback: keep getting feedback from the customer to develop effective software

• Simplicity: Develop a simple system that will work efficiently in present time

• Application of XP

• Small projects :It is useful in small projects consisting of small teams as face to face
meeting is easier to achieve

• Projects involving new technologies or research projects: The project which has
changing requirements and technical problems , so XP is used to complete this type of
projects

XP Practices

• Code review: it detects and corrects code efficiently, it suggests pair programming

• Testing: It suggests test driven development

• Incremental development: development takes place in increments

• Simplicity : simplicity makes easier to develop code

• Design: good quality design is important to build good quality product

• Integration testing: It helps to identify bugs at the interfaces of different

functionalities

SCRUM OVERVIEW

• It applies to any project with aggressive deadlines, complex requirements

• In scrum project move forward via a series of iterations called sprints

• It encourages team to learn through experiences, slef organize while working on a
problem and reflect on their wins and looses to continuously improve

Example of scrum events

• Before starting the first sprint

• Product owner writes down the high level requirements called epics from the
customer

• The scrum master writes them into a product backlog and initates an estimation and
prioritization session with senior developers and testor

• Now he starts to breakdown the high level requirements into user stories, lets assume
he got 8 story

• With this he plans and invites for the first sprint planning meeting

Sprint 1 –Day 0

• During sprint planning, product owner presents product backlog from the highest
priority to lower

• Team clarifies open questions, and then discusses whether they have enough capacity,
skills etc

• After this they commit to complete stories 1,2,3,6,7,8 until the end of the sprint

• After the meeting the scrum master calls the team to define details of how the items
are going to be implemented

• The resulting tasks are written down and every member selects a task to work on

Sprint1-Day 1

• In the morning whole team comes together for their daily meeting

• Everyone speaks about what they achieved so far and what they are planning to
achieve today and shares blockages if any

• If there are any blockages scrum master will take care of it

• After 15 minutes everyone goes back to work

Sprint 1-Day 2
• Again the daily scrim meeting

• In afternoon one of the scrum team members is stuck in a task, He calls product
owner and discusses

• The scrum team mutually finds solution and carries on to work

Sprint –Day 14

• The final day scrum master invites the team for sprint review

• The product owner checks whether the software or product meets his expectations and
if the features are documented as required

• At the end he draws the conclusion

❑ 1,3,6 finished as expected

❑ 2 and 7 couldnot finish in time

❑ 8 has some tasks that have to be redone

❑ In the afternoon team gets together for sprint retrospective and discusses what went
well and what could be improved

❑ One of the feedback was trust issue. The scrum master guides the team on mutual
trust for better results.

Sprint 2-Day 1

• The product owner adds new item to the product catalog

• If suppose the additional items include extra feature in story 8

• Then product owner invites the team for meeting for sprint 2

• The team discusses and commits to stories with the guidance of scrum master and the
second sprint begins

CEREMONIES

• List of all the key ceremonies a scrum team might partake in:

• Organize the backlog: it is known as backlog grooming, the event is the responsibility
of the product owner, their job is to drive the product towards its product vision and
 have constant pulse on the market and the customer. He or she maintains the list using
feedback from user and the development team to help prioritize and keep the list clean
and ready to be worked on any given time

SPRINT PLANNING

• Here scrum team comes together to understand to understand the prioritized

product backlog items and how they map to the product goals

• It can take up to 4 hours

• Sprint planning meetings set out precisely what the team will accomplish during the
sprint. The Product Owner is responsible for bringing company feedback and an up-
to-date and prioritized product backlog to the meeting.

SPRINT

• The projects that follow scrum delivers work in short bursts called sprints

• It takes on average 2 weeks

• It has several roles, one of them is project owner- who maintains and prioritize a list
of required project deliverables known as product backlog

• The product owner finds out the interest of stakeholder and at the beginning of each
sprint, works with project team to decide which deliverables should be tackled next

• This is the heartbeat of the scrum

DAILY SCRUM

• It occurs everyday for 15 minutes

• Here team meets and discusses about progress of their work

• The team has to answer:

• What I did yesterday

• What am I doing today

• Are there any blockers with my work

 SPRINT REVIEW

• On the last day of the sprint

• Sprint review and retrospective ceremonies need to occur

• It brings scrum team, product owners, stakeholders, inspector gadget to review what
has been accomplished

• It takes upto 2 hours

SPRINT RETROSPECTIVE

• It provides better feedback on improvements for quality and effectiveness

• Once the team agrees on improvements, they should be taken up and addressed as
soon as possible

QUESTIONS

1. Explain sprint ceremonies

2. Explain the roles in SCRUM

ACTIVITY 3

Explain the ceremonies in XP and roles in XP(10)