Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Introduction to Agile & scrum

903 views

Published on

Introduction to Agile & scrum, but a bit from an HR perspective.
This presentation was given at "JobInfo" as some background material for a better understanding of recruitment in an agile world.

Published in: Business, Technology
  • Be the first to comment

Introduction to Agile & scrum

  1. 2. Elad Sofer Agile coach CSM CSP http://blog.thescrumster.com [email_address] Introduction to Agile & Scrum Inspect Adapt Do
  2. 4. Requirements Design Implement Test Acceptance Analysis Deliver
  3. 5. The waterfall development model originates in the manufacturing and construction industries The first description of waterfall is a 1970 article by Winston W. Royce Royce presented this model as an example of a flawed, non-working model "I believe in this concept, but the implementation described above is risky and invites failure" [Royce 1970]
  4. 6. Changes in basic assumptions Division of work to specialized teams (specification, design and testing) is efficient It is possible to “collect” or even “know” all the requirements up-front The harder we plan and analyze in the beginning, the less there’s change in the project and the more successful the project. There is change always and responding to it is vital. Uncertainty is best reduced by learning from actual implementation Requirements evolve as customers’ and our knowledge increases – based on experience Cross-functional teams reduce the amount of handovers and are more productive Product development process can be defined as a predictable and repeatable process Product development is an evolving and adaptive process
  5. 8. Values
  6. 9. Agile Principles 1/2 <ul><ul><li>Our highest priority is to satisfy the customer through early and continuous delivery of valuable software </li></ul></ul><ul><ul><li>Welcome changing requirements , even late in development. Agile processes harness change for the customer’s competitive advantage. </li></ul></ul><ul><ul><li>Deliver working software frequently , from a couple of weeks to a couple of months, with a preference to a shorter timescale. </li></ul></ul><ul><ul><li>Business people and developers must work together daily throughout the project. </li></ul></ul><ul><ul><li>Build project around motivated individuals . Give them the environment and support they need, and trust them to get the job done. </li></ul></ul><ul><ul><li>The most efficient and effective method of conveying information to and within development team is face-to-face conversation . </li></ul></ul>
  7. 10. <ul><li>Working software is the primary measure for progress . </li></ul><ul><li>Agile processes promote sustainable development . The sponsors, developers, and users should be able to maintain a constant pace indefinitely. </li></ul><ul><li>Continuous attention to technical excellence and good design enhances agility. </li></ul><ul><li>Simplicity – the art of maximizing the amount of work not done – is essential. </li></ul><ul><li>The best architectures, requirements, and designs emerge from self-organizing teams . </li></ul><ul><li>At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. </li></ul>Agile Principles 2/2
  8. 11. Scrum
  9. 12. Philosophy behind scrum <ul><ul><li>Not a methodology!!! – Problem exposure framework. </li></ul></ul><ul><ul><li>Understanding that we cannot predict the future. </li></ul></ul><ul><ul><li>One size does not fit all. </li></ul></ul><ul><ul><li>Constant improvement. </li></ul></ul><ul><ul><li>Transparency </li></ul></ul><ul><ul><li>Team work </li></ul></ul><ul><ul><li>Empirical approach </li></ul></ul><ul><ul><li>Fun !!! </li></ul></ul>
  10. 13. Scrum process overview
  11. 14. spiral (waterfall) vs. iterative
  12. 15. Scrum product owner - Responsibilities <ul><ul><li>Defines the features of the product </li></ul></ul><ul><ul><li>Defines release dates and content </li></ul></ul><ul><ul><li>Responsible for ROI. </li></ul></ul><ul><ul><li>Prioritizes features </li></ul></ul><ul><ul><li>Can change features and priority once every predefined interval. </li></ul></ul><ul><ul><li>Decides what will be worked on in each iteration </li></ul></ul><ul><ul><li>Accepts or rejects results. </li></ul></ul>
  13. 16. Scrum product owner – Characteristics <ul><ul><li>Visionary. </li></ul></ul><ul><ul><li>Leader & Team player </li></ul></ul><ul><ul><ul><li>Not a control freak </li></ul></ul></ul><ul><ul><li>Good business understanding. </li></ul></ul><ul><ul><li>Good communication skills </li></ul></ul><ul><ul><ul><li>With teams. </li></ul></ul></ul><ul><ul><ul><li>With customers. </li></ul></ul></ul><ul><ul><li>Comfortable with change. </li></ul></ul>
  14. 17. The scrum master - Responsibilities <ul><li>Responsible for the scrum process. </li></ul><ul><li>Protects the team. </li></ul><ul><li>Helps removing impediments. </li></ul><ul><li>He is standing at the nexus between: </li></ul><ul><ul><ul><li>The product management that believes that any amount of work can be done. </li></ul></ul></ul><ul><ul><ul><li>Developer’s that have the willingness to cut quality to support the managements belief. </li></ul></ul></ul>
  15. 18. The scrum master - Characteristics <ul><ul><li>Natural leader & Team player </li></ul></ul><ul><ul><ul><li>Does not require formal authority. </li></ul></ul></ul><ul><ul><li>Very good “soft” skills. </li></ul></ul><ul><ul><ul><li>Communication. </li></ul></ul></ul><ul><ul><ul><li>Influence. </li></ul></ul></ul><ul><ul><li>Understanding of ScrumAgile. </li></ul></ul><ul><ul><ul><li>Certification has nothing to do with it! </li></ul></ul></ul><ul><ul><li>Teacher Facilitator. </li></ul></ul><ul><ul><li>Open minded. </li></ul></ul><ul><ul><li>Problem solver. </li></ul></ul>
  16. 19. The team - Responsibilities <ul><li>Typically 5-9 people </li></ul><ul><li>Cross-functional: </li></ul><ul><ul><ul><li>Programmers, testers, UI designers, etc. </li></ul></ul></ul><ul><li>Members should be full-time </li></ul><ul><ul><ul><li>May be exceptions (e.g., database administrator) </li></ul></ul></ul><ul><li>Teams are self-organizing </li></ul><ul><li>Membership should change as little as possible </li></ul><ul><ul><ul><li>only between sprints </li></ul></ul></ul>
  17. 20. The team member - Characteristics <ul><li>A REAL team player. </li></ul><ul><li>Willing to try and learn new skills. </li></ul><ul><li>Shares openly, admits problems, reliable. </li></ul><ul><li>Cares about others and . </li></ul><ul><ul><li>Respects & appreciates diversity. </li></ul></ul><ul><li>Win-Win mindset: </li></ul><ul><ul><ul><li>Not afraid of conflicts but thrives for consensus. (not compromise) </li></ul></ul></ul><ul><ul><li>A listener. </li></ul></ul>
  18. 21. Scrum is fit for… <ul><ul><li>Projects that want to: </li></ul></ul><ul><ul><ul><li>Deal with changes. </li></ul></ul></ul><ul><ul><ul><li>Increase profits. </li></ul></ul></ul><ul><ul><ul><li>Increase quality. </li></ul></ul></ul><ul><ul><li>Projects sizes such as: </li></ul></ul><ul><ul><ul><li>1 team. </li></ul></ul></ul><ul><ul><ul><li>100 teams. </li></ul></ul></ul><ul><ul><li>Organization that: </li></ul></ul><ul><ul><ul><li>Want to improve. </li></ul></ul></ul><ul><ul><ul><li>Willing to learn. </li></ul></ul></ul><ul><ul><ul><li>Want to succeed. </li></ul></ul></ul>

×