Loading presentation...

Present Remotely

Send the link below via email or IM


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.



An introduction into Agile and Scrum Development

Ramon Noordeloos

on 29 December 2012

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of AgileScrumIntro

Introduction Agile & Scrum AGILE What's this "Agile" stuff? "Agile Development" is an umbrella term for several iterative and incremental software development methodologies.

While each of the agile methods is unique in its specific approach, they all share a common vision and core values.

The Agile Manifesto introduced the term in 2001. (cc) photo by medhead on Flickr Agile is not... Analysis Requirements System Design Code Unit test Integration test Sprint
1-4 weeks Product
Backlog Sprint
Backlog Potentially shippable
Product increment 24 hrs Daily Scrum
Meeting Scrum Traditional Development Each day during the sprint, a project status meeting occurs. This is called a daily scrum, or the daily standup. During the meeting, each team member answers three questions:

- What has been achieved since the last meeting?
- What will be achieved before the next meeting?
- Any impediments? Sprint Planning Meeting Held by the team at the onset of each sprint in which the team reviews the product backlog, agrees upon which items can be completed during the sprint and moves those items to the sprint backlog. The Sprint Sprint Review & Demo Sprint Retrospective Scrum Events & Artifacts SCRUM The Agile Manifesto We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value: Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan That is, while there is value in the items on
the right, we value the items on the left more! Daily Scrum Scrum board Burn Down Chart Product backlog Sprint backlog User Story sprint 1 sprint 2 sprint 3 Release 1 sprint 4 sprint 5 sprint 6 Release 2 sprint 0 Initiation phase 1. Product owner Stakeholders 2. Scrum master Scrum team - Process Champion
- Impediment Remover
- Buffer (shields the team) - Subject Matter expert
- Business Advocate
- End User Advocate
- Customer Advocate
- Communicator
- Decision Maker The product owner is responsible for maximizing return on investment by identifying product features - Self organizing
- Cross functional
- 100% dedicated
- Co-located
- Committed and Accountable What's this "scrum" stuff? Scrum is an iterative and incremental Agile software development method for managing software projects and product or application development. Jeff Sutherland Ken Schwaber - 5 to 9 members Estimated Fixed Scope Scope Budget Schedule Schedule Budget Waterfall Agile Waterfall VS Agile development Acceptance test Release Time Design Code Test Release A "sprint" is a time-frame in which a set of development tasks, estimated and agreed upon by the team, are coded, tested and deemed ready for production.

Sprints are typically 1-4 weeks in duration Held at the end of each sprint to provide project stakeholders transparency into work completed as well as a change to provide immediate feedback that could turn into work during the next sprint Team only meeting to review and discuss the previous sprint. This meeting should focus on the development process and is meant to be an open forum for opinions and process improvement The Scrum Master helps the product group learn and apply Scrum to achieve business value. The Scrum Master does whatever is in their power to help the team be successful! The team builds the product that the customer is going to use. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 12 Principles of the Agile manifesto Agile is a mindset! Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. more predictability
more productivity
more quality
more value
more risk control
satisfied customers
engaged employees
less waste
continuous improvement
shorter Time To Market Agile provides In order to <benefit>
As a <role>
I want <feature> In order to be able to
keep on shopping

As a customer

I want my chosen items
to be saved Agile References The Scrum Guide http://agilemanifesto.org Agile Manifesto http://scrum.org An opportunity to eliminate planning An opportunity to avoid processes An open door for scope creep An excuse to start without proper project initiation and preparation An excuse to produce NO documentation Agile Methods in 2011 3. Development team W e d o n ’ t n e e d a n a c c u r a t e d o c u m e n t , w e n e e d a s h a r e d u n d e r s t a n d i n g epic epic epic user story user story user story user story user story High
priority Low
priority epic epic epic user story user story user story user story user story High
priority Low
priority user story user story user story user story Sprint planning meeting Sprint Backlog Product backlog Source: VersionOne-StateofAgileSurvey2011
Full transcript