Jax Sql Saturday Scrum presentation #130

  • 361 views
Uploaded on

 

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
361
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
  • ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
  • ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
  • ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
  • ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
  • ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
  • 1. Has collaborative working relationship with the Product Owner (PO) as part of the SCRUM team2. Works directly with the PO with no intermediary3. Usually has a skill specialization but interacts with all skillsets within the SCRUM team4. Has no "Command and Control” authority over the manner / approach to which work is completed5. Is responsible for championing SCRUM, removing SCRUM team impediments, keeping the team and the PO operating within the SCRUM framework, and keeping events time-boxed
  • Characteristics1.) Self-organizing teams2.) Product progresses in a series of month-long “sprints”3.) Requirements are captured as items in a list of “product backlog”4.) No specific engineering practices prescribed5.) Uses generative rules to create an agile environment for delivering projects6.) One of the “agile processes”
  • ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
  • ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
  • ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
  • ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
  • ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
  • Although project results have improved slightly over the last few years, the Standish Group's Chaos Report tells us that 72% of projects fail or are challenged. Further, 45% of features implemented are never used, and 19% are rarely used. The most disturbing part is that practices known to drive more successful project outcomes are frequently not adopted. Many of these practices are labeled under the umbrella term agile development.
  • ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Transcript

  • 1. I am a DBA! Why do I care about Scrum?Christopher DailyDirector, Corporate DevelopmentFidelity National Financial 1
  • 2. Agree or Disagree Question 1Question 1: – Processes and tools are absolutely critical to the success of a productAgile thinkers would say… – Processes and tools are important, but we puts more value in individuals and their interactions with each other 2
  • 3. Agree or Disagree Question 2Question 2: – Comprehensive documentation is necessary in order to accurately deliver a high-quality productAgile thinkers would say… – Working software is a better measure of the quality of a product than comprehensive documentation 3
  • 4. Agree or Disagree Question 3Question 3: – To ensure a successful delivery, you must first have a detailed contract describing exactly what is to be deliveredAgile thinkers would say… – Collaboration with the customer is the best way to achieve a successful delivery 4
  • 5. Agree or Disagree Question 4Question 4: – Having a well-thought-out, complete plan is needed to achieve your products goals in a timely mannerAgile thinkers would say… – Since change is a near certainty, how we respond to change is more valuable than adhering to an initial plan 5
  • 6. Why am I here? This presentation is intended to communicate why it is important for specialists (such as DBA, professional testers, automation specialists, etc.) to understand a little more about the Scrum movement. I will discuss what Scrum is, and why you should care. 6
  • 7. What is Scrum? 7
  • 8. What is Scrum? One doubter’s quote…“I really wanted to hate this Scrum thing when went into thetraining. I am pretty happy with the way I work and mycurrent processes but I have to admit, this process producesefficiency and results. I examine my personal life andwonder, ‘What else can I Scrum?’”Lisa Lazzaraon Scrum & FNF Scrum Training 8
  • 9. The Agile Manifesto agilemanifestio.org Source: http://agilemanifesto.org/ 9
  • 10. What is Scrum? More Prescriptive more rules to follow RUP Agile XP ScrumScrum XP DSDM Crystal FDD Kanban Kanban RUP and few more… Do Whatever!! More Adaptive fewer rules to follow
  • 11. Pigs and ChickensTeam Members UsersProduct Owner ManagersScrum Master Stakeholders
  • 12. What is Scrum? From the one authority…Scrum is an agile approach to software development. Ratherthan a full process or methodology, it is a framework. Soinstead of providing complete, detailed descriptions of howeverything is to be done on the project, much is left up tothe software development team.Mike Cohn of Mountain Goat Software http://www.mountaingoatsoftware.com/topics/scrum 12
  • 13. What is Scrum? – Utilizes small, cross-functional, self-directed teams (normally 5-7) – Breaks work into list of small, concrete deliverables which are prioritized and estimated by relative effortSM – Eliminates distractions by fixing the work effort for the duration of the sprint – Embraces change by only committing to the work for the sprint duration (2-4 weeks) Source: Google Images 13
  • 14. Scrum Basics The Sprint
  • 15. Scrum Basics No changes to the Sprint Change ChangeChange Change Change 15
  • 16. Scrum is a Framework Highlighting what ails your organization• Scrum will reveal any issues your organization currently experiences, whether known or unknown, through a focus on transparency• Scrum will not correct any issues you currently deal with or uncover 16
  • 17. Scrum FrameworkRoles•Product owner•Scrum Master•Scrum Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts 17
  • 18. Scalability How Scrum works on an enterprise scale• Typical individual teams are 5 - 7 people – Scalability comes from teams of teams• Factors in scaling – Type of application – Team size – Team distribution – Team proficiencies Source: Google Images – Project duration• Scrum has been used on multiple 500+ person projects spanning the entire globe 18
  • 19. Why do I care? 19
  • 20. Sequential Development Risk / Value Comparison Source: ullizee.wordpress.com 20
  • 21. Overlapping Development Risk / Value Comparison Source: ullizee.wordpress.com 21
  • 22. Standish GroupChaos Report Usefulness of Software ProjectsAlthough project resultshave improved slightlyover the last few years, theStandish Groups ChaosReport tells us that 72% ofprojects fail or arechallenged.Further, 45% of featuresimplemented are neverused, and 19% are rarelyused. Source: IBM Development Works 22
  • 23. Standish Group Software Project Overruns Cost TimeOverruns Responses Overruns ResponsesUnder 20% 15.5% Under 20% 13.9%21 - 50% 31.5% 21 - 50% 18.3%51 - 100% 29.6% 51 - 100% 20.0%101 - 200% 10.2% 101 - 200% 35.5%201 - 400% 8.8% 201 - 400% 11.2%Over 400% 4.4% Over 400% 1.1%Average 189% Average 222% Source: Standish Group Report 23
  • 24. Why should you care?• Companies are looking to improve the odds – Get value sooner rather than later – Reduce cost – Reduce risk – Be more revelant• People want more from their job – Pride in what they accomplish – Freedom to do what is right – Contribute to something – Avoid daycare mentality 24
  • 25. Why should you do?"Guess what guys! Its time to embrace the horror! Look, we got front-row tickets to the end of the earth!“ (Rockhound in Armageddon) 25
  • 26. Why should you do?• Stay current on development methodologies• Take advantage of training• Be a positive• Become a valuable team member 26
  • 27. Helpful Websites• Scrum Alliance – http://www.scrumalliance.org/• Scrum.Org – http://www.scrum.org/• Mike Cohn and Mountain Goat Software – http://www.mountaingoatsoftware.com• Coming soon! Agile Jax User Group – http://www.agilejax.org/ 27
  • 28. Any Questions?Thanks for your time. 28