Scribd
Upload
344 views13 pages

Agile Framework

Scrum is a framework to release product / s in small but shippable segments or that promotes development iterations throughout the life-cycle of the project / product. Includes following terminologies - - Pig Roles Chicken Roles Pig Roles These are committed resources, who are responsible for the success or failure for product / project deliverables.

Uploaded by

Deepak Chhabra
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
344 views13 pages

Agile Framework

Scrum is a framework to release product / s in small but shippable segments or that promotes development iterations throughout the life-cycle of the project / product. Includes following terminologies - - Pig Roles Chicken Roles Pig Roles These are committed resources, who are responsible for the success or failure for product / project deliverables.

Uploaded by

Deepak Chhabra
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 13

Agile Methodology - Framework

By Deepak Chhabra
What is Agile

 A framework to release product/s in small but shippable segments


or that promotes development iterations throughout the life-cycle of
the project/product.
 Includes following terminologies

• Scrum
• Sprint
• Timeboxing

Copyright Infogain Corporation, 2008 -2-


Scrum?

 These are daily meetings of a fixed amount of time where folks


meet face to face or through video conferencing, in case located at
different geographies. (Management perspective – to manage
software development program/s)
• Have two roles
– Pig Roles
– Chicken Roles

Copyright Infogain Corporation, 2008 -3-


Pig Roles

 These are committed resources, who are responsible for the


success or failure for product/project deliverables.
• Scrum Master (Usually a Project Manager)
• Product Manager/Owner or both (Stakeholders Representatives)
• Team (includes dev’s, QA’s, Tech Writers etc.)

Copyright Infogain Corporation, 2008 -4-


Chicken Roles

 These are involved/included resources, who are not responsible for


the success or failure for product/project deliveries but can and
only share ideas, views/reviews, feedback and priorities etc.
• User (End user of product)
• Business representative (internal/external)
• Stakeholders

Copyright Infogain Corporation, 2008 -5-


Sprint?

 Product Backlogs (All remaining items/Priorities)


 Sprint Backlogs (Frozen Requirements)

 Develop, Test, Release shippable product

 Burn Down Chart (This includes remaining number of items left for

current sprint or product backlog items.)

Copyright Infogain Corporation, 2008 -6-


Sprint Components

 Sprint Components
• Sprint Planning (Timeboxed for couple of hours)
• Daily Sprint as Scrum (Timeboxed for 15 minutes, irrespective of the
team size.)
• Sprint Retro (Timeboxed for 04 hours)

Copyright Infogain Corporation, 2008 -7-


What happens in Sprint

 Every team member has to answer three questions.


• Since yesterday, what he/she has done till today.
• Plans for tomorrow.
• Any showstopper/road blocker or issue, someone on hands to discuss.

Copyright Infogain Corporation, 2008 -8-


Timeboxing

 Any activity, which has to be done over a fixed amount of time,


irrespective of length of activity is know as Timeboxed.
 E.g. Exams are Timeboxed.

Copyright Infogain Corporation, 2008 -9-


Agile - Advantages
 Customer satisfaction by rapid, continuous delivery of useful software
 Working software is delivered frequently (weeks rather than months)
 Working software is the principal measure of progress
 Even late changes in requirements are welcomed
 Close, daily cooperation between business people and developers
 Face-to-face conversation is the best form of communication (Co-location)
 Projects are built around motivated individuals, who should be trusted
 Continuous attention to technical excellence and good design
 Simplicity
 Self-organizing teams
 Regular adaptation to changing circumstances

Copyright Infogain Corporation, 2008 - 10 -


Agile - Criticism
 Lack of structure and necessary documentation (Tailored Processes)
 Requires too much cultural change to adopt

 Very difficult to develop realistic estimates of work effort needed to

provide a quote, because at the beginning of the project, sometimes, no


one knows the entire scope/requirements
 Increases the risk of scope creep due to the lack of detailed requirements

documentation

Copyright Infogain Corporation, 2008 - 11 -


?

Thanks!!

Copyright Infogain Corporation, 2008 - 12 -


This document has been prepared by INFOGAIN CORPORATION
Reproduction and/or distribution without permission of Infogain is prohibited.

You might also like