springpeople introduction to agile and scrum

© SpringPeople Software Private Limited, All Rights Reserved. © SpringPeople Software Private Limited, All Rights Reserved.

Introduction to Agile & Scrum

© SpringPeople Software Private Limited, All Rights Reserved.

Traditional Software Development

• It’s a sequential life cycle, commonly known as “The waterfall model”.

• Begins with a detailed planning phase, where the end product is carefully thought through, designed, and documented in great detail.

• The team estimates how long the development will take

• Stakeholders reviews the plan & approves/rejects it.

• Once it’s developed, it’s handed over to testing organization.

• Finally release it to your customer


Traditional Software Development

• Strength

– Supremely logical, think before you build, write it all down, follow a plan and keep everything organized well.

• Great Weakness

– Humans are involved


Agile Manifesto - 2001

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:


Principles of Agile Manifesto • Customer satisfaction by rapid delivery of useful software

• Welcome changing requirements, even late in development

• Working software is delivered frequently (weeks rather than months)

• Sustainable development, able to maintain a constant pace

• Close, daily co-operation between business people and developers

• Face-to-face conversation is the best form of communication (co-location)

• Projects are built by motivated individuals, who should be trusted

• Continuous attention to technical excellence and good design

• Self-organizing teams

• Regular adaptation to changing circumstances


SCRUM


Foundations of the Scrum

• There is a cross-functional team that is stable and 100% dedicated

• The team decides how to get the work done. It’s a self organizing team.

• The team plans it’s sprints one at a time, at the start of each sprint.

• The Product owner decides what should be produced.

• The team decides how much it can produce in each sprint.

• The team’s target in a sprint is shared, clear and does not change.

• The team tries to achieve it’s target. But it may over-deliver or under-deliver, based on how the sprint plays out.

• Each sprint is a time box. It’s length never extended.

• Each sprint produces “potentially shippable product”, meaning thoroughly tested, defect-free and “done.”

• There is a definition of Done.

• At the end of each sprint, we inspect and adapt product and process


A Normal day in Scrum Master’s Life

•Remove impediments/resolve problems •Break up fights/quarrels •Act as a team mom •Report team data •Facilitate(Team, Meetings) •Help out where needed •Educate the organization •Drive organizational change


Become a Scrum Master In 2 Days Flat

Attend the 2-Days “Agile/Scrum Workshop”

View Complete Details

http://www.springpeople.com/courses/regular/agile-software-development-using-scrum-workshop-training-course.php


Who will benefit?

Developers, Project Managers, Business or System Analysts, and Technical

Managers who wish to learn the philosophy and practices of Scrum.

View Complete Details

http://www.springpeople.com/courses/regular/agile-software-development-using-scrum-workshop-training-course.php


Q & A

[email protected] +91 80 65679700

www.springpeople.com

A SpringSource Certified Partner and

VMware Authorized Training Center

mailto:[email protected]

http://www.springpeople.com/

springpeople introduction to agile and scrum

Education

development working

agile scrum

self organizing team

crossfunctional team

practices of scrum

scrum masters life

end product

shippable product