Disciplined agile software delivery is an evolutionary (iterative and incremental) approach to delivery which regularly produces high quality

software in a cost effective and timely manner. It is performed in a highly collaborative and self-organizing manner within an appropriate governance framework, with active stakeholder participation to ensure that the team understands and addresses the changing needs of its stakeholders. Disciplined agile delivery teams provide repeatable results by adopting just the right amount of ceremony for their situation.

1.Scrum is a lightweight agile process framework used primarily for managing and controlling iterative and incremental projects of all types.

2.Scrum is: Lightweight because it has few prescribed elements i) Three roles: Team, Scrum Master (often a Project Manager), Product Owner

ii) Four meetings: Sprint Planning, Daily Scrum, Review,Retrospective iii)Four artifacts: Product Backlog, Sprint Backlog, Burndown chart , Impediment Backlog.

3. Agile because it maximizes responsiveness to changing customer needs

4. A process framework because it is not a process, but a collection of practices and concepts around which a process can be built

XP is an Agile software development method which is intended to improve productivity and introduces checkpoints where new requirements can be adopted. The concept of XP is to focus on: 1.Goals 2.Activities 3.Values 4.Principles 5.Practices

1.The Goal of XP is to produce High Quality Software. 2.XP attempts to reduce the cost of changes by having multiple short development cycles ,rather than one long one.

1.Listening:Programmers must listen to the customers, to understand what "business logic " is needed . 2.Designing:To avoid complexity the software structure and complexity is designed. ii.Lets assume its a very complex software.To design this sw architecture is divided into separate components.Good designing will remove lots of dependencies between the sw components.This means changes in one component will not effect the other sw component. 3.Coding: 4.Testing:

Communication : The goal is to give all developers a shared view of the system which matches the view held by the customer. Simplicity : XP Encourages starting with the simplest solution , extra functionality can be added later. Feedback:From customer ,team.It is closely related to communication and simplicity. Courage:It enables developers to feel comfortable with refactoring their code when necessary. Respect: Includes respect for others as well as self respect.

Assuming Simplicity : This is about treating every problem as if its solution were extremely simple. Embracing Change:Its about not working against changes but embracing them.

Pair Programming : Knowledge Transfer:

Two programmers work together at one workstation . Sharing knowledge about the software with the team.

Test driven development: Negative tests are written even before the code is coded.

1.Eliminating Waste 2.Amplifying Learning 3.Deciding as Late as Possible 4.Delivering as Fast as Possible 5.Empowering the Team 6.Building Integrity In 7.Seeing the Whole

1.Scrum Roles. 2.Scrum Artefacts. 3.The Sprint Meetings. 4.Scrum Framework Complete Picture. 5.Starting Scrum.

1.Scrum Roles

1.Managing the Stakeholders. 2.Gathering the requirements. 3.Managing and prioritizing the Product Backlog. 4.Working on a shared vision. 5.Managing the release plan. 6.Accepting or rejecting the software at the end of each iteration. 7.Helps to define the meaning of Done.

1.Process Facilitator . 2.Managing Impediment Backlog. 3.Empowering and shepherding the team. 4.Helps to create information radiators. 5.Helps in building self organizing team.

Self-organising teams.

2.Scrum Artefacts
S c rum m a nd a te s o nly fo ur a rte fa c ts : 1.P ro d uc t B a c klo g 2.S p rint B a cklo g 3.B urnd o wn Cha rt 4.Im p e d im e nt B a c klo g

Product Backlog
1.Product Backlog is a list of work items. 2.Items may be added to the backlog by anyone ,But Product Owner will determine the order in which they will be executed by the team. 3.Requirements are emergent, & we do not and cannot know up front every detail about what we want in a product. 4.It's a living document and requires constant grooming to keep it current and useful. 5.Many new items will be added over time. 6.existing items are disaggregated to multiple, smaller items; 7.some items may be removed on realizing that a desired feature is no longer needed. 8.items need to be sized in order to determine the likely relationshipbetween value, time and cost. 9.Its preferable, to create and maintain the Product Backlog as a set of stories. 10.The stories are commonly written from the perspective of a user of the product.

Product Backlog
Items
1.Software Development Methodology Agile Presentation 2.Gmat Preparation 3.Login Functionality for Loans 4.Submitting an application for loan 5.Web service call to 3rd party to retrieve info 6.Processing the loan 7.Booking the loan 8.Sending generated documents to user.

Size
18 20 12 10 14 18 15 14

Task Board / Sprint Backlog Stories To Do In Progress Done

Agile Presentation

i.3 Chapters PPT Preparation . ii.Clear Understanding of 3 Chapters. 1.Coding Jsp ,Controller Classes 2.Verifying data with DB values 3.Home Page 4.Error Page

1st chapter PPT

Login Functionality

Coding Jsp pages

Gmat

Take 2 Mock Tests

P hy s ica l re p re s e nt a t io n o f t he lis t o f wo rk t he y ha v e c o m m it t e d to Do d uring t he curre nt s p rint.

Sprint Burndown Chart

1.Sprint 1 will contain 50 story points and 14 days for previous Sprint backlog. 2.Teams use the sprint Burndown chart to track the product development effort remaining in a sprint and to monitor its progress. 3.X axis to display working days , Y axis to display remaining effort. 4.It will be a leading indicator of whether it will meet its commitment at the end of the sprint or not.

1.A Product-Burndown-Chart depicts story points of all user stories in the

so called product backlog. 2.The chart displays story points for each completed sprint, so it depicts the completion of requirements over time. 3.Backlog and Product-Burndown-Chart is usually updated at the end of each sprint. 4.New user stories can be added and/or removed before each sprint planning meeting. 5.Used to show the team and stakeholders how many sprints will be needed to implement all remaining user stories or how many user stories can be completed in the remaining time.

Impediment Backlog
1.Telephone is not working. 2.Daily metting rooms are not available. 3.Required softwares are not installed in team members system. 4.Need clarification on some User story by customer. 5.Conflicts among team members.

1.The im p e d im e nt b a cklo g is s im p ly the c urre nt lis t o f t hings t ha t a re p re v e nt ing t he t e a m fro m p ro gre s s ing o r im p ro v ing. 2.The s e a re t hings the S c rum Ma s t e r m us t b ulld o ze o ut o f t he wa y in he r ne v e r-e nd ing q ue s t t o he lp t he t e a m b e t he b e s t t he y ca n.

3.The Sprint Meetings

1.The s p rint is the he a rt b e a t o f t he S crum c y cle . 2.It is b o o km a rke d b y sprint planning a t t he s t a rt a nd b y t he sprint review a nd sprint retrospective a t t he e nd . 3.The le ngt h o f t he s p rint is fixe d a nd is ne v e r e xte nd e d . Mo s t S crum t e a m s c ho o s e t wo , t hre e o r fo ur we e ks a s t he ir s p rint d ura t io n. 4.E a ch d a y d uring t he s p rint t he te a m ho ld s a daily Scrum meeting. E v e ry m e e t ing in S crum is s t ric t ly time-boxed. This m e a ns t ha t is ha s a m a xim um d ura t io n.

Sprint Planning - Part 1

1.Pa rt 1 o f s p rint p la nning (S P 1) is re a lly a d e ta ile d requirements workshop. 2.The p ro d uc t o wne r p re s e nts the s e t o f fe a ture s he wo uld like a nd the te a m a s ks q ue s tio ns to und e rs ta nd the re q uire m e nts in s uffic ie nt d e ta il to e na b le the m to c o m m it to d e liv e ring the fe a ture d uring the s p rint. 3.The te a m a lo ne d e c id e s wha t it c a n d e liv e r in the s p rint,ta king into a c c o unt the s p rint d ura tio n, the s ize a nd c urre nt c a p a b ilitie s o f its m e m b e rs , its d e finitio n o f DONE., a ny kno wn ho lid a y s o r le a v e d a y s a nd a ny a c tio ns it c o m m itte d to d uring the re t ro s p e c tiv e he ld p rio r to this . 4.The p ro d uc t o wne r m us t b e p re s e nt d uring this m e e ting to le a d the te a m in the right d ire c tio n a nd to a ns we r q ue s tio ns a nd the y will ha v e m a ny.

5.The S c rum Ma s te r m us t e ns ure tha t a ny o t he r s ta ke ho ld e r ne e d e d to he lp the te a m und e rs t a nd the re q uire m e nts is p re s e nt o r o n c a ll.

6.Any ne w b a c klo g ite m s fo r inc lus io n in the c urre nt s p rint a nd no t p re v io us ly e s tim a te d will b e s ize d im m e d ia te ly d uring this m e e ting. This no t, ho we v e r, a n e xc us e to a v o id g ro o m ing the b a c klo g!

7.At the e nd o f S P 1 the te a m c o m m its to the P ro d uc t Owne r wha t t he y b e lie v e the y c a n d e liv e r in the fo rm o f running tested features.

8. My re c o m m e nd a t io n to m o s t te a m s is to d o commitment-based planning.

9.The b a c klo g ite m s the te a m ha s c o m m itte d to is c a lle d the selected product backlog.

Sprint Planning - Part 2

1.If p a rt 1 is a re q uire m e nts wo rks ho p , p a rt 2 o f s p rint p la nning (S P 2) is a design workshop.

2. In this s e s s io n the te a m c o lla b o ra te s to c re a te a high-le v e l d e s ign o f the fe a ture s it ha s c o m m itte d to d e liv e r.

3.An o utc o m e o f this s e s s io n is the s p rint b a c klo g,

4.This is m o s t o fte n re p re s e nt e d o n a p hy s ic a l task board.

Daily Scrum Meeting

1.The d a ily S crum m e e t ing is NOT fo r re p o rt ing p ro gre s s to t he S c rum Ma s t e r o r P ro d uct Owne r o r a ny o ne e ls e . The Pro d uc t Owne r m a y a t t e nd o r m a y no t ! 2.The S crum Ma s t e r m a ke s s ure , t ha t e a ch t e a m m e m b e r ha s s igne d up fo r s o m e wo rk fo r the ne xt 24 ho urs . 3.Any im p e d im e nts t o d o ing t his wo rk a re b ulld o ze d o ut o f t he wa y a s fa s t a s p o s s ib le . 4.The S crum Ma s t e r a ls o e ns ure s t he m e e ting is re s t ric t e d to 15 m inute s . 5.The t e a m m e e ts t o co m m unica te a nd s y nchro nis e it s wo rk. S inc e t he t e a m is co lla b o ra t ing, t his is e s s e nt ia l t o e ns uring c o nt inue d p ro gre s s a nd a v o id ing wo rk b lo c ka ge s . The t e a m will a ls o co nt inuo us ly a s s e s s its o wn p ro gre s s t o wa rd s a chie v ing it s sprint goal.

Sprint Review

1.Its a d e m o ns t ra tio n o f t he ne w fe a t ure s (co d e d , t e s t e d a nd us a b le p ie ce o f s o ft wa re ) t he t e a m ha s co m p le t e d d uring t he s p rint .

2.it s p rim a ry p urp o s e is t o inspect wha t t he t e a m ha s d e liv e re d a nd ga the r fe e d b a ck fro m the a t t e nd e e s t o adapt t he p la n fo r t he s ucce e d ing s p rint.

3.The fo c us o f t he s p rint re v ie w is t he product the t e a m is b uild ing.

4.Pa rt icip a nt s in t he s p rint re v ie w t y p ica lly inc lud e t he p ro d uc t o wne r, t he S crum t e a m , t he S c rum Ma s t e r, m a na ge m e nt , cus t o m e rs a nd d e v e lo pe rs fro m o t he r p ro je ct s .

Sprint Retrospective

1.The retrospective is focussed on the process. 2.The way in which the Scrum team is working together, including their skills and the software development practices and tools they are using. 3.The sprint retrospective is restricted to the members of the Scrum team Product Owner, development team members and ScrumMaster. 4.Purpose is to inspect at a deep level how the team is collaborating and to take action to improve. 5.This often requires deep introspection and sharing, which in turn requires a secure environment. technical that is the performing and safe and

4.Scrum Framework

5.Starting Scrum
Ob v io us ly y o u ne e d a S c rum te a m . This m e a ns a P ro d uc t Owne r, a S c rum Ma s te r a nd fiv e to nine te a m m e m b e rs . The n fo llo w this s e q ue nc e o f s te p s .

1. Tra in the S c rum Te a m in the b a s ic s o f S c rum 2. E s ta b lis h the v is io n 3. Write us e r s to rie s to fo rm the p ro d uc t b a c klo g 4. Ord e r the b a c klo g ite m s b y b us ine s s v a lue 5. S ize the b a c klo g ite m s 6. R e -o rd e r the b a c klo g, a s ne c e s s a ry , b y a d d itio na l fa c to rs 7. Cre a te the initia l re le a s e p la n 8. P la n the firs t s p rint 9. S ta rt s p rinting!