1 / 7

Implementing Agile/Scrum in An “IT” Department…

Implementing Agile/Scrum in An “IT” Department…. It’s Not the Same As in a Software Development Shop. Leading provider of technical training for Automotive, Diesel, Motorcycle & Marine industry 10 Campuses >16,000 Students ~$350 m in Revenue. Software Environment “SMART”

sydney
Télécharger la présentation

Implementing Agile/Scrum in An “IT” Department…

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Implementing Agile/Scrum in An “IT” Department… It’s Not the Same As in a Software Development Shop

  2. Leading provider of technical training for Automotive, Diesel, Motorcycle & Marine industry 10 Campuses >16,000 Students ~$350 m in Revenue Software Environment “SMART” Custom Student Management System Progress Open Edge Arch 2.3 Million lines of code PeopleSoft G/L Software Development 46 FTE’s + Contractors 6 SCRUM Teams App Support Universal Technical Institute

  3. Align Teams to the Business • Each Scrum Team supports 1-3 Business Functions • Benefits to the Business • Team becomes an Expert • Business views IT as a True “Partner” • Greater Visibility • Involved in setting the Priorities • Easier to Justify Project Costs • Eliminate Waste • Change is “Ok” • Speed – Time to Use DIESEL

  4. “IT” Scrum Team Makeup • Core Team Members • Scrum Master / PM • Business Analyst – CRITICAL Role • Developers • QA Analyst – Must Have • Ancillary Team Members • Business Owners • User Acceptance Testing • Network Engineer • Service Desk Staff

  5. Key Points • Team Members • Can ONLY Shift at Sprint Boundaries • Do NOT Steal Resources mid-Sprint • Can be Remote… • We do it all the time • Capacity Utilization • Never Load at 100% • Production Support • 6 hours / day

  6. Key Points • Large Projects • Can Absolutely be Done!!!!! • Break Down into Smaller 2 Week Chunks • Allow for “Analysis” and “Design” User Stories • Estimates are for Number of Sprints +/- X

  7. Key Points • Paradigm Shift is HUGE for… • IT Management • Project Managers / PMO • Business Analyst • Centralized Tool • Visibility across Teams • One Source of the Truth • Use a Pilot • Try it out once… • Or twice • Make it Fun • Team Names & Motos • Friendly Competition • And don’t give up

More Related