Agile

AGILE
Based on 4 facts(values) and 12 Principles

1)A methodology or philosophy which has some guidelines and rules for developing a
software
2)A mindset or philosophy that describes a set of principles in Agile Manifesto,
it is a way to build s/w and any changes can be made during project life cycle
3)Frameworks of Agile : SCRUM(widely used),KANBAN,XP
4)KANBAN : used to provide maintainence for existing project
Q)Difference between Agile and other traditional project management?
=>Steps are same in all models(waterfall,iterative,prototype,spiral win win )
=>Waterfall model is sequential in nature and is used in projects that require
longer duration for completion.
In this model the team has to wait until the last process is completed and then
only changes can be made
sow:sign of work
SCRUM
"A better way of building Products"
"A Servant leader"
1)It is adaptive in nature where all steps are done parallely
2)It adapts and fits for a lot of frequent changes...It is lightweight and simple
to understand
3)It works on the principle of : Implement(including design and plan) then
Introspect and move on
4)There is NO BOSS in a scrum
5)Overlapping Development...Scrum is a framework to implement Agile methodology
Scrum is popular because of its parallel development
Q)What process you follow in your company in testing ? scrum used by tester and
developer
SCRUM VALUES : Courage,Focus,Commitment,Respect,Openess
SPRINT
1)It is the time duration(2 to 4 weeks)
2)Sprint timeline is defined once and cannot be changed
3)Scope of sprint is not changed
4)Sprint is the backbone of scrum
5)Sprint and Scrum are time boxing i.e. time bounded
6)NO GAP between consecutive SPRINT
7)After every sprint we get a potentially shippable product
8)Product is designed,coded and tested during sprint
SPRINT BACKLOG
1)Set of tasks broken down into smaller sub-tasks by development team
2)Functionality is broken into smaller tasks
ROLES IN A SCRUM FRAMEWORK(SCRUM TEAM)

1)Product Owner 2) Team 3) A Scrum Master
PRODUCT OWNER
1)Responsible to manage the PRODUCT BACKLOG and prioritize it
2)Product Backlog is the set of requirements owned and managed by the Product Owner
3)New requirements goes inside the Product Backlog
4)Sequence of tasks can be changed in Product Backlog according to requirement
of client only by the Product Owner
5)Product Owner always keeps interacting with the client
6)Role : To make USER STORY and menstion that in product backlog,
To achieve financial goals of the project,
Define the features of the Product and adjust features and priority as needed.
If in Sprint Review its discussed that login page color,button or spelling should
be changed
or J-Unit needs to be changed then that is included by Product Owner
TEAM
1)Size max 9 and min 5 for EASY COMMUNICATION between its members
2)Team is self-oriented,self-directed,focussed,self-organized and goal-oriented
3)Team decides which task to be done from the Product Backlog so Product owner
CANNOT
order team to define which work to be done first or last
4)Team decides the duration of sprint with the help of product owner and scrum
master
5)It includes Developers,Testers
6)Cross-Functional
A SCRUM MASTER : a good listener and soft spoken

1)To take responsibility and care of team from outside distractions and
interruptions and fulfil their requirements(eg laptop)
2)Responsible to create a happy environment and provide them training if required
3)A scrum master works with a Single Team...Scrum is more productive in office
4)Responsibilities to RESOLVE eg : language communication between south and north
Indian people,
fighting between team members,if a team member wants to go in other work then scrum
master has to be informed
and he will decide whether the member will go or not
=>Product is used and accepted by everyone
DAILY STAND-UP MEETING(THE DAILY SCRUM)

1)15 min stand-up call daily
2)Discussion of what all we have done yesterday and what all we have to do
today and which task to be taken from the Product Backlog to be completed in the
day
3)Product owner,scrum-master(facilitator of the meeting) and team attends the
meeting
4)Not for problem solving
BURN UP/DOWN CHART

1)Indicates the progress of the SPRINT...measured in terms of user-story
2)Burn-up : work completed so far
3)Burn-down : leftover task to be completed
SPRINT REVIEW
1)To answer if work completed before or after a SPRINT and how much work is
completed
2)Sprint Review Meeting happens after a sprint ends
3)All members including the CLIENT attends this meeting
4)2 to 3 hours duration or more as required
SPRINT RETROSPECTIVE
1)Which work was done BEST and What we need to learn...Discuss what is and what is
not working
2)Takes place after a Sprint Review...Whole team participates(scrum master,product
owner,team)
3)Done after every sprint...Half an hour duration
4)If work not completed in a SPRINT then remaining work moves in BACKLOG again
after Retrospection
USER-STORY
1)It is an informal general explanation of a s/w feature written from the
perspective of the end user or customer
Specify in sticky notes...As a...I want to...So i can
2)eg LOGIN page,Sign-up,Sign-in,dmin
3)User story made by PRODUCT OWNER
=>Story-Board : progress of task
=>Story-Point : calculation of duration taken to do a task by team
=>If TIMELINE increases,cost of project increases and if timeline decreases cost

also decreases
=>Product Increment : set of finished products
Q)product owner=client?
Q)With whom Product Owner talk about Product Backlog?
Q)What would you do during a review if the product-owner does'nt agree to the
feature you implemented?
Q)Who is responsible to make sprint and divide work for a single sprint?
Q)How to set sprint?How to track progress in sprint?
Q)Product owner will be a single person or can be a group of persons?
Q)What process is followed in your company by testers and developers? Scrum
Q)If work not completed within the sprint then remaining work moves to Product
Backlog or Sprint Backlog?
Q)If user-story is not completed in assigned sprint then?
Q)Where do we practice Agile and Scrum and which tools and s/w used to do this?
Q)Who gives user-story to team from the Sprint backlog?
Q)Member and duration for each type?
Q)After every sprint ,is there a sprint review meeting?
Q)Scrum-Master qualifications and experience?Who will present explanation of sprint
shippable s/w to the client?
Q)Incase Scrum-Master is unavailable,would still Daily Standup Meeting be
conducted?
Q)What if work completed before the sprint?
Q)What is velocity,build breaker,scrum ban?
Velocity depends on our calibre and potential
Q)Who will participate in Sprint Planning and what is its duration?
===================================================================================
=
Assume Harold liked your argument and agreed to proceed with agile on this project.
In his reply, Harold asked for further guidance on how to move forward. Please
reply back with the following:What things will have to change on how this team
operates and how key stakeholders interact or engage on this project. (Hint: as you
have learned, for agile to be successful there are certain prerequisites and it
poses certain challenges for leadership/business stakeholders as well)The team is
new to Agile and based on prerequisites for agile to be successful, please specify
if you and your team need any help or training etc. If none, please state that.As
of my knowledge, our team members have some experience in web development but none
in mobile development.Nobody on team has performance testing experience or User
experience expertise.People with an open mindset are the only key pre-requisite for
the successful implementation of an Agile method. In fact, I would not suggest that
you add too many tools to a team that is not used to them. Instead, if the team
has the open mindset and the requisite attitude then train and start them on an
Agile method.Any Agile method will do - Kanban, XP, Scrum. Most of the developers
and testers have offices on different floors of the building and generally work in
their office. Since the team is scattered then some amount of technology needs to
betaken upfront. The most important aspects of good agile project management is
judgement and responding to change. With judgement, I mean the ability to see
risks(good perception and listening skills) before they become issues and coming up
with good strategies to mitigate these risks. Having the courage to accept that you
do not have all answers are a prerequisite for Agile to be successful. If everyone
just applies common sense in thinking value of incremental change the right tools
will automatically get commissioned on the way.

Agile

Uploaded by

Copyright:

Available Formats

Agile

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

Agile

Uploaded by

Copyright:

Available Formats

AGILE

Based on 4 facts(values) and 12 Principles

SCRUM VALUES : Courage,Focus,Commitment,Respect,Openess

ROLES IN A SCRUM FRAMEWORK(SCRUM TEAM)

A SCRUM MASTER : a good listener and soft spoken

DAILY STAND-UP MEETING(THE DAILY SCRUM)

BURN UP/DOWN CHART

=>If TIMELINE increases,cost of project increases and if timeline decreases cost

You might also like