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
Agile – scrum +
Agile – Scrum + Alon Lahav SVP engineering
Agile iterative and incremental development, whererequirements and solutions evolve throughcollaboration between self-organizing, cross-functional teams
Agile ManifestoIndividuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan
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
ScrumScrum is an iterative and incremental agilesoftware development framework formanaging software projects and product orapplication development.
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
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
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
Sprint Planning Meeting - Participants• The whole team• The product owner• Scrum Master
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.
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
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!
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.
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
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
Daily Scrums• start exactly on time• standing up• Up to 15 minutes• update the taskboard during the daily scrum• update time estimates
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
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
release planning• Product owner defines a list of acceptance thresholds• Time estimate the top X (or whatever) stories in the product backlog• Acceptance test