39
Agile/Scrum Methodology None but, an acceleration on productivity Md. Hasan Basri Software Consultant

Agile/Scrum Methodology Gains Your Productivity

Embed Size (px)

Citation preview

Agile/Scrum MethodologyNone but, an acceleration on productivity

Md. Hasan BasriSoftware Consultant

The Agile movement proposes alternatives to traditional project management. Agile approaches are typically used in software development to help businesses respond to unpredictability.

What Is Agile?

Still not clear!

Team Based Incremental Iterative Value Driven Frequent Delivery Production Quality Inspect & Adapt

What is Agile Software Development?

Does it provide steps?

So, It guided some steps, Right?

So, How it differ from traditional waterfall?

Alright, But it’s very strict

Let’s talk about Scrum!

Scrum is an agile software development model based on multiple small teams working in an intensive and interdependent manner.

The term is named for the scrum formation in rugby, which is used to restart the game after an

event that causes play to stop, such as an infringement.

Scrum Framework

Product Owner Responsibility

Scrum Master Responsibility

The Scrum Team

7 +/- 2 Cross functional Full time Self organizing Empowered Trust

Five levels of Planning

Story points Story points vs. mandays Estimation meetings Planning poker Reference stories

Estimation

User Stories

Scrum Task Board Template

Sprint Plan (Priority v/s Size)

Three Levels of Estimating

Estimating using story points

The most common way of estimating the size of user stories in Scrum is by allocating story points. Story points are just numbers drawn from a pool of numbers of a set size e.g. a story could have 1, 2, 3, 5, 8, 13, 20, 40 or 100 story points.

Poker Planning for Estimation

Estimate Size / Drive Duration

SizeDuratio

nCalculatio

n

250 mh

250/25 = 10 days

Velocity = 25

mh/day

Product Release Cycle

Scrum Suggested Meetings

Sprint Planning Meeting

Daily Scrum Meeting Agenda

Test Model

Backlog Grooming

Sprint Review Meeting

What went well this sprint? What could we improve next sprint? Dev Environment, working practices,

communication

Sprint Retrospective

Requires one day or less of work. Remaining effort is re-estimated daily, typically in

hours. During Sprint Execution, a point person may

volunteer to be primarily responsible for a task. Owned by the entire team; collaboration is expected.

Spring Task

Indicates total remaining team task hours within one Sprint Re-estimated daily, thus may go up before going down Intended to facilitate team self-organization Fancy variations, such as itemizing by point person or adding trend

lines, tend to reduce effectiveness at encouraging collaboration Seemed like a good idea in the early days of Scrum, but in practice

has often been misused as a management report, inviting intervention. The ScrumMaster should discontinue use of this chart if it becomes an impediment to team self-organization.

Burndown showing over commitment

Tracks the remaining Product Backlog effort from one Sprint to the next.

May use relative units such as Story Points for Y axis. Depicts historical trends to adjust forecasts.

Product / Release Burndown Chart

Factors in scaling:

Type of application Team size Team dispersion Project duration

Scrum has been used on multiple 500+ person projects.

Scalability

Individuals whocommit to work together to reach a common goal.

What's a team?

Hard to plan No commitment Bad communication Competition and blaming Less value delivered

Problems

Cross Functional Team

en.wikipedia.org/wiki/Agile_software_development http://cvcedhlab.hypotheses.org/54 scrummethodology.com www.mountaingoatsoftware.com › Agile www.allaboutagile.com/how-to-implement-scrum-in-10-easy-steps/ http://www.slideshare.net/jaaronfarr/scrum-agile-for-everyone?related=4 http://www.slideshare.net/hareshkarkar/overview-of-agile-methodology?

related=5 http://www.slideshare.net/infolock/agile-presentation-6607073?related=6 www.scrumguides.org/docs/scrumguide/v1/scrum-guide-us.pdf http://mplaza.pm/downloads/Scrum Training Manual.pdf http://www.tutorialspoint.com/software_engineering/

software_engineering_pdf_version.htm

Please excuse me if I missed some body’s reference unintentionally.

Used References