What is Framework?

Set of instructions or project which we have to deploy or particular rules that we have to follow.

Examples of Framework:-
Several different types of software frameworks exist. Popular examples include ActiveX and .
NET for Windows development, Cocoa for Mac OS X, Cocoa Touch for iOS, and the Android
Application Framework for Android

Agile Model:
Agile SDLC model is a combination of iterative and incremental process models with focus on
process adaptability and customer satisfaction by rapid delivery of working software
product. Agile Methods break the product into small incremental builds. These builds are
provided in iterations.

What is Scrum?
Scrum is an agile process framework for managing complex knowledge work, with an initial
emphasis on software development, although it has been used in other fields and is slowly starting
to be explored for other complex work, research and advanced technologies.

A Scrum Team is a collection of individuals (typically between five and nine members) working
together to deliver the required product increments. The Scrum framework encourages a high
level of communication among team members, so that the team can: Follow a common goal.

1. Product Owner:
Product owner is a scrum development role for a person who represents the
business or user community and is responsible for working with the user
group to determine what features will be in the product release.
As the liaison between the development team and customers, the product
owner must collaborate closely with both groups to ensure there is a clear
understanding of what features are needed in the product or application.
Because there may be a variety of types of customers and users, the product
owner must have a firm understanding of the business domain and the
varying needs of different types of users.

The scrum sprint begins with a planning meeting in which the product owner
conveys and prioritizes the requirements or features of the application to the
development team . The product owner helps prioritize the user stories from
the backlog so that the team knows which stories to work on during the scrum
sprint. The product owner is responsible for answering any questions from the
development team to help clarify any details as they are developing the
application.

Scrum product owner responsibilities include:

 Defining the features of the application.

 Prioritizing features of the application.

 Adjusting the features and priority as needed after each sprint or iteration.

 Accepting or rejecting work results.

 Keeping customers or users apprised of status and getting their feedback.

2. Scrum Master:
A scrum master is the facilitator for an agile development team. Scrum is a methodology that
allows a team to self-organize and make changes quickly, in accordance with agile principles.
The scrum master manages the process for how information is exchanged.

In product development, team members huddle together each morning for

a stand-up meeting where they review progress and essentially restart the
project. During the daily meetings, which are sometimes called "scrums," the
scrum master asks the team members these three questions:

1. What did you do yesterday?

2. What will you do today?
3. Are there any impediments in your way?

Although the title of scrum master sounds powerful, the scrum master is not
the project leader and is not held accountable for outcomes. The team as a
whole is responsible for outcomes.
That does not mean that the job is easy, however. The scrum master is
responsible for:

1. Helping the team to reach consensus for what can be achieved during a
specific period of time. (See sprint)
2. Helping the team to reach consensus during the daily scrum.
3. Helping the team to stay focused and follow the agreed-upon rules for
daily scrums. (See pigs and chickens)
4. Removing obstacles that are impeding the team's progress.
5. Protecting the team from outside distractions.

Technical Team:-

DEVELOPERS and TESTERS

What is Sprint:It is a process of deliver the product.

Sprint is one timeboxed iteration of a continuous development cycle. Within a Sprint, planned
amount of work has to be completed by the team and made ready for review

In Scrum, all work is confined to regular work cycles, known as iterations or

sprints. Sprints are normally two weeks long, but can be as short as one
week, or as long as four weeks. Originally, all sprints were 30 days long, but
the methodology has since changed to favor the shorter sprints.

Product teams are able to devise their own sprint time. If a team finds a
two-week sprint too difficult, a one-week sprint should be attempted.

The goal of each sprint is to create a potentially shippable product

increment, even if that increment is extremely basic. Since the time frame of
the sprints are so short, the team is forced to work on the function or
feature that is most essential.

The Scrum methodology is iterative and incremental, which means that each
iteration builds on the work from the previous incremental. This is why
multiple sprints are needed. As soon as one sprint ends, there are the
required meetings, and the next sprint starts right away.
Each sprint begins with the sprint planning meeting. This meeting brings the
product owner and team together to discuss what tasks should be moved
from the product backlog into the sprint backlog. One thing to remember,
the manager never speaks in the meetings!

What is Sprint Planning?

Sprint planning is an event in the Scrum framework where the team determines the product
backlog items they will work on during that sprint and discusses their initial plan for completing
those product backlog items.

What is Sprint Meeting?

The sprint planning meeting is a collaborative meeting between the ScrumMaster (who
facilitates the meeting), the Product Owner (who clarifies the product backlog and their level of
importance), development team (to define work necessary to complete items on the product
backlog).

What is BACKLOG?

The Backlog – The backlog can include almost anything, including

new functions or bugs/errors. The items on the backlog must be
small enough to be able to be completed in the sprint time (usually
two weeks).

Product Backlog

An ordered list of everything that must be done for a product, listed

from most important to least important.
 Sprint Backlog

An ordered list of tasks taken from the product backlog during the
sprint planning meeting.

Daily Scrum Meeting

Everyday there is a daily Scrum meeting, often called the standup (because
it is encouraged that you stand up). The Scrum development team, the
product owner, and the ScrumMaster all meet at the same time and place
each day for this short 15-minute meeting.

The standup meeting (it is called that because it is short and no one needs
to sit down) is run by the ScrumMaster, who asks the team a few simple
questions.

What did you accomplish yesterday?

What do you plan to accomplish today?

Are there any problems or obstacles that need to be addressed?

Many teams maintain a sprint task list, a sprint burndown chart, and an
impediments list. It is not uncommon to uncover new tasks that are
necessary to achieve the sprint goals.

The product owner should attend the daily standups, if possible. Although
some teams excel at meetings where the product owner is absent, this
meeting is meant to change old habits of working separately and
independently.

Sprint Review Meeting

Once a sprint has been completed, the team holds the sprint review meeting
to prove it has developed a working product increment. The sprint review
meeting is four hours long. The product owner will attend this meeting, as
will any interested stakeholder.

This meeting should have a live demo of the new shippable feature, and
should not just be a report. After the demo, the product owner reviews the
commitments made at the planning meeting and decides what is now done
and complete.

The ScrumMaster helps the product owner turn their feedback into new
product backlog items, which the product owner will prioritize.

The sprint review meeting is the meeting that stakeholders should attend, as
it gives them the opportunity to see the product in a live demo and ask any
questions they may have.

What is Retrospective Meeting?

An Agile retrospective is a meeting that's held at the end of an iteration in Agile software
development (ASD ). During the retrospective, the team reflects on what happened in the
iteration and identifies actions for improvement going forward.

Sprint Retrospective Meeting

The ScrumMaster will often lead this meeting, and find ways to maintain full
transparency so team members can be honest with their findings. It is
important the team members feel safe, and that they can discuss anything
with the team.

Participating in a sprint retrospective

This meeting is action-oriented and should answer three main questions:

1. What was successful about the sprint?

2. What would we want to change?

3. How can we make that change happen?

Before the retroactive begins, the members of the team should think about
these three questions beforehand. Notes should also be taken.

After these three questions are asked, additional topics could be discussed,
such as:

Results – How did they compare with what was expected?

People – How did the team perform?

Relationships – How did the team work with each other?

Processes – How did processes for support and development work?

Tools – Are the current tools working for the team? Should new tools be
implemented, and if so, what kind?

Productivity – Can the team increase productivity, and if so, how?

One of the Scrum rules is the retrospective should last no longer than 45
minutes per week of the sprint, so normally 90 minutes for a two-week
sprint.

It can often be difficult for the teams to be open, and if this happens, the
ScrumMaster should ask questions to get people talking.

Sprint Meetings

Beginning of Sprint – Sprint Planning Meeting

Daily – Daily Scrum Meeting or Standup

End of Sprint – Sprint Review

 End of Sprint – Sprint Retrospectiv

USER stories:

What is a user story

In Agile methodology ‘User Story’ is a unit of work that should be completed in
one sprint. Smaller than that it’s a task, more than week(s) of work is Epic or
Theme.

The agile recommendation is to break down a set of user stories into smaller ones, containable
into a single sprint duration, or ideally, a user story shouldn’t last more than a week.