Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Data Con LA 2019 - Scrum Overview by Sonia Macias

195 vues

Publié le

Does your team run scrum projects; but you haven't been trained in scrum? Are you tasked with creating user stories, but you aren't sure how to write a user story? You got to run scrum! Prior to 2001 the basic issue was that software development framework wasn't working. Projects were not being delivered on time, requirements were not met, costs exceeded budgets, business community was losing confidence in their technology team. In 2001 seventeen software developers met to discuss a lightweight development method. The Agile software development would deliver frequent incremental software with business value with rapid feedback and responding to change. Scrum is an agile framework for software development. Scrum ceremonies are collaborative time boxed events to getting working software delivered. Scrum roles are distinct to a Scrum Master, Product Owner, and the Development Team. The scrum session will provide the participant with an overview of running a project in scrum.

Publié dans : Technologie
  • Login to see the comments

Data Con LA 2019 - Scrum Overview by Sonia Macias

  1. 1. WE RUN SCRUM SCRUM OVERVIEWData Con LA 2019 University of Southern California
  2. 2. INTRODUCTION Sonia Macias, MBA, CSM, CSPO, PMP, CISA, CPA B.S. Marshall School of Business, USC Scrum Master / Product Owner / Project Manager Scrum Transformation Global Entertainment Studios: Fox Sports and Entertainment, Disney, Warner Bros., Universal Studios, Universal Music Group, Sony Pictures Entertainment
  3. 3. AGENDA Agile • Agile • What is Agile? • Agile Values • Agile 12 Principals Scrum Tools • Scrum Team • Scrum Ceremonies • Scrum User Story • Scrum Product Backlog • Scrum Certifications • Jira • Confluence
  4. 4. 9/2/2019 AGILE SOFTWARE DEVELOPMENT HISTORY PRE-2001 2001 . Source: PM World360 Magazine Software Development wasn’t working • Long lag times from requirements to software delivery  Iterative development  Frequent delivery of business value  Rapid feedback and willingness to change Response to Change
  5. 5. 9/2/2019 WHAT IS AGILE? Framework for software development Based on the Agile Manifesto set of values and principles
  6. 6. 9/2/2019 6 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. AGILE MANIFESTO 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  7. 7. 9/2/2019 7 4. Business people and developers must work together daily throughout the project. AGILE MANIFESTO 5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6. The most efficient and effective method of conveying information to and within a development team is face-to- face conversation.
  8. 8. 9/2/2019 8 7. Working software is the primary measure of progress. AGILE MANIFESTO 8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9. Continuous attention to technical excellence and good design enhances agility.
  9. 9. 9/2/2019 9 10. Simplicity--the art of maximizing the amount of work not done--is essential. AGILE MANIFESTO 11. The best architectures, requirements, and designs emerge from self-organizing teams. 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
  10. 10. 9/2/2019 10 SCRUM S • Teams deliver products in short cycles • Fast feedback • Continual improvement • Rapid adaptation to change C R U M AN AGILE FRAMEWORK
  11. 11. SCRUM TEAM Vision 9/2/2019 11 PRODUCT OWNER DEVELOPMENT TEAM SCRUM MASTER • Maximizes the value of the product • Manages the Product Backlog Build Scrum Coach • Deliver an increment of “Done” product at the end of each Sprint • Self organizing • Servant leader • Facilitates removing blockers • Helps everyone unders Scrum practices, rules values
  12. 12. 9/2/2019 12 SCRUM CEREMONIES SPRINT IS THE HEART OF THE SCRUM
  13. 13. 9/2/2019 13 SCRUM CEREMONIES FRAMEWORK TO GET WORK DONE Sprint Planning • Team planning meeting to determine the work to complete in the upcoming • Monthly planning and re-planning Daily Stand Up (Scrum) • Transparency, knowledge, and communication • Time-boxed 15 minutes  What did you do yesterday? (Jira Story #)  What will you do today? (Jira Story #)  Are there any blockers in your way? (Jira Story #)
  14. 14. 9/2/2019 14 SCRUM CEREMONIES DEMONSTRATE THE DONE FUNCTIONALITY Demo completed work done in Sprint Product Owner accepts/rejects User Story based on acceptance criteria
  15. 15. 9/2/2019 15 SCRUM CEREMONIES RETROSPECTIVE Inspection and create a plan for improvement 1. What worked well for us? 2. What did not work well for us? 3. What actions can we take to improve our process going forward?
  16. 16. 9/2/2019 16 SCRUM USER STORY Requirement for any functionality or feature • “As a <user role/customer>, I want to < goal to be accomplished> so that I can <reason of the goal>”. • Example: As an Ad Sales Planner, I want to enter the Deal Number in the Ad Sales dashboard, so that I can search the ad sales by deal number.
  17. 17. 9/2/2019 17 SCRUM ACCEPTANCE CRITERIA Accepted conditions or business rules which the functionality or feature should satisfy and meet “Given some precondition, when I do some action, then I expect the result”. Example: When I open the Ad Sales dashboard and enter the deal number, then the ad sales by deal number displays. Estimate User Story Points – 1 point = 1 day or less of work, 4 points = 4 days of work or less
  18. 18. 9/2/2019 18 SCRUM JIRA • Create user stories, plan sprints, and distribute tasks across Scrum team • Transparency
  19. 19. 9/2/2019 19 SCRUM CONFLUENCE • Landing Page for project and team wiki • Track Scrum Ceremonies, Sprint Scrum status • Tightly integrated with Jira
  20. 20. 9/2/2019 20 SCRUM CERTIFICAITONS Distinguish yourself as a Scrum practitioner. Certified Scrum Master (CSM) Certified Product Owner (CSPO) Certified Scrum Developer (CSD) Scrum Alliance training courses: https://www.scrumalliance.org/get-certified
  21. 21. 9/2/2019 21 SCRUM REFERENCES Agile Alliance. (2019). Principles based on the Agile Manifesto. Retrieved from https://www.agilealliance.org/agile101/practices-timeline/ Schwaber, K., Sutherland, J. (2017, November). The Definitive Guide to Scrum: The Rules of the Game. The Scrum Guide. Retrieved from https://www.scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide- US.pdf#zoom=100 Scrum Alliance. (2018). Scrum Alliance. Retrieved from https://www.scrumalliance.org/ Software Testing Help. (2018). What is User Story and Testing Acceptance Criteria (Examples). Retrieved from https://www.softwaretestinghelp.com/user-story-acceptance- criteria/
  22. 22. THANK YOU DATA CON LA ORGANIZERS, SPONSORS, VOLUNTEERS, PARTICIPANTS & USC!
  23. 23. FIGHT ON! Linkedin: https://www.linkedin.com/in/sonia-macias- mba-csm-cspo-pmp-cisa-cpa-74aa99/ E-mail: kjlh1234567@gmail.com kjlh: kindness, joy, love, & happiness!

×