Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Agile and Scrum

A quick introduction to Agile methodology and Scrum framework
by

Bayram Karagoz

on 16 March 2017

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile and Scrum

Use of Agile Management Tools
SCRUM
When is Scrum Appropriate?
Framework

Empirical
https://tr.wikipedia.org/wiki/Scrum
Feedback Loop
Transparency
Inspection
Adaptation
Waterfall Vs Agile
Manifesto for Agile Software Development
Individuals and interactions
over processes and tools
Working software
over comprehensive documentation
Customer collaboration
over contract negotiation
Responding to change
over following a plan
http://agilemanifesto.org/
Agile Methodology
Waterfall
Scrum
Scrum Master
Scrum Dev Team
Product Owner
Ken Schwaber
Jeff Sutherland
Principles of Agile Methodology
12
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
1
Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
2
Deliver working software frequently, from a couple of weeks to a couple of months, with preference to the shorter timescale.
3
Business people and developers must work together daily throughout the project.
4
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
5
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
6
Working software is the primary measure of progress.
7
8
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9
Continuous attention to technical excellence and good design enhances agility.
10
Simplicity -- the art of maximizing the amount of work not done -- is essential.
11
The best architectures, requirements, and designs emerge from self-organizing teams.
12
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Advantages of Agile
Change is embraced
End-goal can be unknown
Faster, high-quality delivery
Strong team interaction
Customers are heard
Agile and Scrum
Dis
advantages of Agile
Planning can be less concrete
Team must be knowledgeable
Time commitment from developers
Documentation can be neglected
Final product can be very different
The New New Product Development Game
1986
Advantages of Scrum
More transparency and project visibility
Increased team accountability
Easy to accommodate changes
Increased cost savings
Dis
advantages of Scrum
Risk of scope creep
Team requires experience and commitment
The wrong Scrum Master can ruin everything
Poorly defined tasks can lead to inaccuracies
Product Owner
ROI
Product Vision
Value Maximizer, Mini-CEO
What to do? , Accountable
Owns Product Backlog
Stakeholder Management
Prioritizing All The Work
Only 1 Person
Trade off
Scrum Development Team
Cross-functional Group
Potentially shippable product increment
Self-organizing
3-9 Developers
How to do?
Estimation
Decompose
Owns Sprint Backlog
One room
Scrum Master
Has no management authority
Doesn't have PM role
Facilitator
Coaching
Process Management
Remove Impediments
Servant Leader
Only 1 Person
How can I help you?
Scrum Master's Checklist
http://scrummasterchecklist.org/
The Power of Scrum Master
Product Backlog
List of Product Features
Evolves, Dynamics, Living
Owned & Prioritized By PO
Not a list of tasks
Product Backlog Item (PBI)
SM makes it visiable
Everyone can add items to PB
Written from User Stories or Use Case Scenarios
Sprint Backlog
Forecast
Defines the work
Owned by Dev Team
Emerges
Sprint Planing
Daily Scrum
Sprint Review
Sprint Retrospective
Sprint Planning Meeting
Part 1:What?
Part 2:How?
8 hours (timeboxed)
Output:
Sprint Goal
Sprint Backlog

Daily Scrum Meeting
15 min (timeboxed)
Only for Dev Team
Same time&place
Sprint Review Meeting
Stakeholder
4 hours (timeboxed)
Live Demo
Inspect the Increment
Feedback
O:Revised PB
Sprint Retrospective
3 hours (timeboxed)
inspection of people, relationships, tools, process
Designed by Bayram Karagöz
Agile
Full transcript