2. Agile
iterative and incremental development, where
requirements and solutions evolve through
collaboration between self-organizing, cross-
functional teams
3. Agile Manifesto
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
4. The Idea
• Focus on getting things done
• Accept that they may mistakes along the way
• The best way to find those mistakes is to stop
thinking about the software at the theoretical
level
5. Scrum
Scrum is an iterative and incremental agile
software development framework for
managing software projects and product or
application development.
9. Roles
• Product Owner - voice of the customer, writes
the user stories prioritizes them, and adds
them to the product backlog
• Development Team - self-organizing
• Scrum Master
11. product backlogs - Definition
• A prioritized list of requirements, or stories,
• or features. Things that the customer
wants, described using the customer’s
terminology (user stories).
• Owner - product owner
• Shared Excel document / Google doc
12. Backlog Item
• ID - auto-incremented number
• Name – a short, descriptive name of the story
• Importance – the product owner’s importance rating
for this story (Any story that the product owner
believes has a remote possibility of being included in
the next sprint should have a unique importance level)
• Initial estimate – the team’s initial assessment of how
much work is needed to implement this story (in man
days)
• Notes
• The user story or how to demo
13. Sprint Planning Meetings
• purpose - to give the team enough
information to be able to work in undisturbed
peace for a few weeks, and to give the
product owner enough confidence to let them
do so.
• Outcome:
– A sprint goal
– A sprint backlog
– A defined sprint demo date
15. Sprint planning meeting agenda
• 30 mins - Product owner goes through sprint goal
and summarizes product backlog.
• 90 mins - Team time-estimates, and breaks down
items as necessary. Product owner updates
importance ratings as necessary. Items are
clarified.
• 60 mins - Team selects stories to be included in
sprint.
• 60 mins – starting breakdown of stories into
tasks.
16. Defining the sprint length
• once you have decided what length you
like best, stick to it for an extended
period of time.
• 3 week sprints
• everyone knows that every 3 weeks
there is a release
17. Sprint Goal
• should be in business terms, not technical
terms.
• not already been achieved
• everybody in the company (not only top-level
management) can knows what the company is
doing – and why!
19. Sprit Backlog
• A snapshot of stories from the product
backlog. A list of stories that the team will
commit to for this sprint
• The team decides how many stories to include
in the sprint.
20. Sprint Planning meeting
• index cards with the stories and put them up
on the wall (or a large table).
• Importance order
• For every “sprint poetical” story:
– Brake to tasks
– Estimate each task
– Summarize the tasks to the Initial estimate
22. After Sprint Planning meeting
• index cards can be carried right off to the
team room and be used as a wall-based
taskboard
• After the sprint planning meeting, the Scrum
master manually updates the Excel-based
product backlog
24. Daily Scrums
• start exactly on time
• standing up
• Up to 15 minutes
• update the taskboard during the daily scrum
• update time estimates
25. sprint demos why
• The team gets credit for their accomplishment
• Other people learn what your team is doing.
• attracts vital feedback
• forces the team to actually finish stuff and
release it
26. sprint retrospectives
• 1 – 3 hours
• Participants: The product owner, the whole
team, scrum master
• The Scrum master shows the sprint backlog
and, with help from the team, summarizes the
sprint. Important events and decisions
• Round table
• estimated vs. actual
• selected 5 process improvements to focus on
27. release planning
• Product owner defines a list of acceptance
thresholds
• Time estimate the top X (or whatever) stories
in the product backlog
• Acceptance test
traced back to 1957, In 1974, a paper by E. A. Edmonds introduced an adaptive software development process. Agile Manifesto 2001
In 1986, Hirotaka Takeuchi and IkujiroNonaka described a new approach to commercial product development that would increase speed and flexibility, based on case studies from manufacturing firms in the automotive, photocopier and printer industries
כולם מעורבים, בעמידה לא נרדמים, הכרטיסים מכילים את כל הפרטים מה-backlog
