Что такое findslide.org?

FindSlide.org - это сайт презентаций, докладов, шаблонов в формате PowerPoint.

Для правообладателей

Обратная связь

Email: Нажмите что бы посмотреть

Презентация на тему Lesson 7 guideline. AGILE Scrum Methodology. Основные понятия

Содержание

2. Основные понятияAGILE Scrum Methodology
3. Scrum – это гибкая методология, которая фокусируется
4. CHARACTERISTICSSelf-organizing teamsProduct progresses in a series of
5. THE AGILE MANIFESTO–A STATEMENT OF VALUESSource: www.agilemanifesto.org
6. PUTTING IT ALL TOGETHER
7. SPRINTSScrum projects make progress in a series
8. Source: “The New New Product Development Game”
9. NO CHANGES DURING A SPRINTPlan sprint durations
10. SCRUM FRAMEWORK
11. SCRUM FRAMEWORKProduct backlogSprint backlogBurndown chartsArtifacts
12. PRODUCT OWNERDefine the features of the productDecide
13. THE SCRUMMASTERRepresents management to the projectResponsible for
14. THE TEAMTypically 5-9 peopleCross-functional:Programmers, testers, user experience
15. THE TEAMTeams are self-organizingIdeally, no titles but rarely a possibilityMembership should change only between sprints
16. SCRUM FRAMEWORK
17. Sprint planning meetingBusiness conditionsTeam capacityProduct backlogTechnologyCurrent product
18. SPRINT PLANNINGTeam selects items from the product
19. THE DAILY SCRUMParametersDaily15-minutesStand-upNot for problem solvingWhole world
20. EVERYONE ANSWERS 3 QUESTIONSThese are not status for the ScrumMaster
21. THE SPRINT REVIEWTeam presents what it accomplished
22. SPRINT RETROSPECTIVEPeriodically take a look at what
23. START / STOP / CONTINUEWhole team gathers and discusses what they’d like to:Start doingStop doingContinue doing
24. SCRUM FRAMEWORK
25. PRODUCT BACKLOGThe requirementsA list of all desired
26. A SAMPLE PRODUCT BACKLOG
27. THE SPRINT GOALA short statement of what
28. MANAGING THE SPRINT BACKLOGIndividuals sign up for
29. MANAGING THE SPRINT BACKLOGAny team member can
30. A SPRINT BACKLOGTasksCode the user interfaceCode the
31. A SPRINT BURNDOWN CHARTHours
32. Hours403020100MonTueWedThuFriTasksCode the user interfaceCode the middle tierTest the middle tierWrite online helpMon816812TuesWedThurFri50
33. SCALABILITYTypical individual team is 7 ± 2
34. SCALING THROUGH THE SCRUM OF SCRUMS
35. Скачать презентацию
36. Похожие презентации

Основные понятияAGILE Scrum Methodology

Главная
Информатика
Lesson 7 guideline. AGILE Scrum Methodology. Основные понятия

ДАТА МЕНЕДЖМЕНТ ТЕСТИРОВАНИЕ ПРОГРАММНОГО ОБЕСПЕЧЕНИЯКИЕВ 2012

Scrum – это гибкая методология, которая фокусируется на business valueПозволяет быстро и

CHARACTERISTICSSelf-organizing teamsProduct progresses in a series of month-long “sprints”Requirements are captured as

THE AGILE MANIFESTO–A STATEMENT OF VALUESSource: www.agilemanifesto.org

SPRINTSScrum projects make progress in a series of “sprints”Typical duration is 2–4

Source: “The New New Product Development Game” by Takeuchi and Nonaka. Harvard

NO CHANGES DURING A SPRINTPlan sprint durations around how long you can

SCRUM FRAMEWORKProduct backlogSprint backlogBurndown chartsArtifacts

PRODUCT OWNERDefine the features of the productDecide on release date and contentBe responsible

THE SCRUMMASTERRepresents management to the projectResponsible for enacting Scrum values and practicesRemoves

THE TEAMTypically 5-9 peopleCross-functional:Programmers, testers, user experience designers, etc.Members should be full-timeMay

THE TEAMTeams are self-organizingIdeally, no titles but rarely a possibilityMembership should change only between sprints

Sprint planning meetingBusiness conditionsTeam capacityProduct backlogTechnologyCurrent product

SPRINT PLANNINGTeam selects items from the product backlog they can commit to

THE DAILY SCRUMParametersDaily15-minutesStand-upNot for problem solvingWhole world is invitedOnly team members, ScrumMaster,

EVERYONE ANSWERS 3 QUESTIONSThese are not status for the ScrumMaster

THE SPRINT REVIEWTeam presents what it accomplished during the sprintTypically takes the

SPRINT RETROSPECTIVEPeriodically take a look at what is and is not workingTypically

START / STOP / CONTINUEWhole team gathers and discusses what they’d like to:Start doingStop doingContinue doing

PRODUCT BACKLOGThe requirementsA list of all desired work on the projectIdeally expressed

THE SPRINT GOALA short statement of what the work will be focused

MANAGING THE SPRINT BACKLOGAny team member can add, delete or change the

A SPRINT BACKLOGTasksCode the user interfaceCode the middle tierTest the middle tierWrite

Hours403020100MonTueWedThuFriTasksCode the user interfaceCode the middle tierTest the middle tierWrite online helpMon816812TuesWedThurFri50

SCALABILITYTypical individual team is 7 ± 2 peopleScalability comes from teams of

Слайды презентации

Слайд 2
Основные понятия
AGILE Scrum Methodology

Слайд 3
Scrum – это гибкая методология, которая фокусируется на

Scrum – это гибкая методология, которая фокусируется на business valueПозволяет быстро

business value
Позволяет быстро и последовательно предоставлять работающие части проекта

заказчику
Каждые две недели любой заинтересованный человек может участвовать на показе текущей версии
Заказчик задает приоритеты. Команда самооопределяется, чтобы производить наиболее важную для заказчика функциональность
Scrum задает только общие правила управления проектом

Что такое Scrum

Слайд 4 CHARACTERISTICS
Self-organizing teams
Product progresses in a series of month-long

CHARACTERISTICSSelf-organizing teamsProduct progresses in a series of month-long “sprints”Requirements are captured

“sprints”
Requirements are captured as items in a list of

“product backlog”
No specific engineering practices prescribed
Uses generative rules to create an agile environment for delivering projects
One of the “agile processes”

Слайд 5 THE AGILE MANIFESTO–A STATEMENT OF VALUES
Source: www.agilemanifesto.org

Слайд 6 PUTTING IT ALL TOGETHER

Слайд 7 SPRINTS
Scrum projects make progress in a series of

SPRINTSScrum projects make progress in a series of “sprints”Typical duration is

“sprints”
Typical duration is 2–4 weeks or a calendar month

at most
A constant duration leads to a better rhythm
Product is designed, coded, and tested during the sprint

Слайд 8 Source: “The New New Product Development Game” by

Source: “The New New Product Development Game” by Takeuchi and Nonaka.

Takeuchi and Nonaka. Harvard Business Review, January 1986.

Rather than

doing all of one thing at a time...

...Scrum teams do a little of everything all the time

Requirements

Design

Code

Test

Слайд 9 NO CHANGES DURING A SPRINT
Plan sprint durations around

NO CHANGES DURING A SPRINTPlan sprint durations around how long you

how long you can commit to keeping change out

of the sprint

Change

Слайд 10 SCRUM FRAMEWORK

Слайд 11 SCRUM FRAMEWORK

Product backlog
Sprint backlog
Burndown charts

Artifacts

Слайд 12 PRODUCT OWNER
Define the features of the product
Decide on

PRODUCT OWNERDefine the features of the productDecide on release date and

release date and content
Be responsible for the profitability of the

product (ROI)
Prioritize features according to market value
Adjust features and priority every iteration, as needed
Accept or reject work results

Слайд 13 THE SCRUMMASTER
Represents management to the project
Responsible for enacting

THE SCRUMMASTERRepresents management to the projectResponsible for enacting Scrum values and

Scrum values and practices
Removes impediments
Ensure that the team

is fully functional and productive
Enable close cooperation across all roles and functions
Shield the team from external interferences

Слайд 14 THE TEAM
Typically 5-9 people
Cross-functional:
Programmers, testers, user experience designers,

THE TEAMTypically 5-9 peopleCross-functional:Programmers, testers, user experience designers, etc.Members should be

etc.
Members should be full-time
May be exceptions (e.g., database administrator)

Слайд 15 THE TEAM

Teams are self-organizing
Ideally, no titles but rarely

a possibility
Membership should change only between sprints

Слайд 16 SCRUM FRAMEWORK

Слайд 17

Sprint planning meeting
Business conditions
Team capacity
Product backlog
Technology
Current product

Слайд 18 SPRINT PLANNING
Team selects items from the product backlog

SPRINT PLANNINGTeam selects items from the product backlog they can commit

they can commit to completing
Sprint backlog is created
Tasks are

identified and each is estimated (1-16 hours)
Collaboratively, not done alone by the ScrumMaster
High-level design is considered

As a vacation planner, I want to see photos of the hotels.

Слайд 19 THE DAILY SCRUM
Parameters
Daily
15-minutes
Stand-up
Not for problem solving
Whole world is

THE DAILY SCRUMParametersDaily15-minutesStand-upNot for problem solvingWhole world is invitedOnly team members,

invited
Only team members, ScrumMaster, product owner, can talk
Helps avoid

other unnecessary meetings

Слайд 20 EVERYONE ANSWERS 3 QUESTIONS
These are not status for

the ScrumMaster

Слайд 21 THE SPRINT REVIEW
Team presents what it accomplished during

THE SPRINT REVIEWTeam presents what it accomplished during the sprintTypically takes

the sprint
Typically takes the form of a demo of

new features or underlying architecture
Informal
2-hour prep time rule
No slides
Whole team participates
Invite the world

Слайд 22 SPRINT RETROSPECTIVE
Periodically take a look at what is

SPRINT RETROSPECTIVEPeriodically take a look at what is and is not

and is not working
Typically 15–30 minutes
Done after every sprint
Whole

team participates
ScrumMaster
Product owner
Team
Possibly customers and others

Слайд 23 START / STOP / CONTINUE
Whole team gathers and

discusses what they’d like to:
Start doing
Stop doing
Continue doing

Слайд 24 SCRUM FRAMEWORK

Слайд 25 PRODUCT BACKLOG
The requirements
A list of all desired work

PRODUCT BACKLOGThe requirementsA list of all desired work on the projectIdeally

on the project
Ideally expressed such that each item has

value to the users or customers of the product
Prioritized by the product owner
Reprioritized at the start of each sprint

This is the product backlog

Слайд 26 A SAMPLE PRODUCT BACKLOG

Слайд 27 THE SPRINT GOAL
A short statement of what the

THE SPRINT GOALA short statement of what the work will be

work will be focused on during the sprint

Database Application

Financial

services

Life Sciences

Support features necessary for population genetics studies.

Support more technical indicators than company ABC with real-time, streaming data.

Make the application run on SQL Server in addition to Oracle.

Слайд 28 MANAGING THE SPRINT BACKLOG
Individuals sign up for work

of their own choosing
Work is never assigned
Estimated work remaining

is updated daily

Слайд 29 MANAGING THE SPRINT BACKLOG
Any team member can add,

MANAGING THE SPRINT BACKLOGAny team member can add, delete or change

delete or change the sprint backlog
Work for the sprint

emerges
If work is unclear, define a sprint backlog item with a larger amount of time and break it down later
Update work remaining as more becomes known