Scrum As An Agile Methodology

2,045 views

Published on

IT Executive Overview of Scum in the IT Organization.

Published in: Technology, Business
1 Comment
2 Likes
Statistics
Notes
No Downloads
Views
Total views
2,045
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
130
Comments
1
Likes
2
Embeds 0
No embeds

No notes for slide

Scrum As An Agile Methodology

  1. 1. Scrum as an Agile Methodology An IT Management Overview By Dave Rognerud
  2. 2. Intrinsic Value of Scrum <ul><li>Scrum focuses on value, leadership, technical excellence, collaboration, and self-emergent social and product behaviors. It uses an agile process that is holistic in its approach to software development and delivery. </li></ul>
  3. 3. Intrinsic Value of Scrum <ul><li>Using Scrum as an agile methodology can rid software development of its current reputation by: [i] </li></ul><ul><li>Reducing process waste (non-value added activity, resource sub-optimization, etc.), </li></ul><ul><li>Reducing product waste (unused features, poor quality, etc.), </li></ul><ul><li>Increasing customer and employee satisfaction, and </li></ul><ul><li>Delivering the right product and services, faster which deliver working products with faster time-to-market and better flexibility to toward change! </li></ul><ul><li>[i] PM Boulevard, Robbins-Gioia, LLC. </li></ul>
  4. 4. Intrinsic Value of Scrum <ul><li>It also focuses resources directly at the business problem that is: </li></ul><ul><li>Gives the Owner Control over solving their business problems. </li></ul><ul><ul><li>Solution are defined, prioritized and authorized by the business. </li></ul></ul><ul><ul><li>Has a committed team dedicated to solving their technology problems </li></ul></ul><ul><ul><li>Business accepts the solution </li></ul></ul><ul><ul><li>and receives working software </li></ul></ul><ul><li>Gives the CIO’s management team real business success. </li></ul><ul><ul><li>It removes from the IT realm problems associated with multiple priorities and shifting needs. </li></ul></ul><ul><ul><li>Reduces logistical resource management nightmares that are perennial issues. </li></ul></ul><ul><ul><li>Highlights impediments to delivering business solutions. </li></ul></ul><ul><ul><li>Helps your organization identify and remove barriers that inhibit project success </li></ul></ul>
  5. 5. What is Scrum? <ul><li>Scrum is an agile, project management light, process used to manage and control software and product development using iterative, incremental practices. Agile methodologies insist on; a fast mode of delivery and shorter project life cycles. It delivers working deployable software, which is accepted by the users, as the key to Scrum’s success. </li></ul>
  6. 6. Keys to Scrum’s success <ul><li>Scrum process uses any one of the Agile tools: XP (eXtreme Programming), AD (Agile Database Techniques), AM (Agile Modeling), or any number of other agile methods. </li></ul><ul><li>Scrum does not dictate which engineering practices must be used. </li></ul><ul><li>Scum may be combined with XP to generate the benefits of agile development with the advantages of simple implementations. </li></ul><ul><li>Scrum, used properly, significantly increases productivity and reduces time to market while facilitating adaptive, empirical systems development. </li></ul>
  7. 7. Scrum principles: <ul><li>Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. </li></ul><ul><li>Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage. </li></ul><ul><li>Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. </li></ul><ul><li>Working software is the primary measure of progress. </li></ul>
  8. 8. Scrum’s own characteristics and practices: <ul><li>Three basic roles: Product Owner, ScrumMaster, and Project Team </li></ul><ul><li>Product Backlog </li></ul><ul><li>Sprint Backlog </li></ul><ul><li>Sprint Planning Meeting </li></ul><ul><li>Daily Scrum Meeting </li></ul><ul><li>Thirty-day iterations, delivering increments of potentially shippable functionality at the end of each iteration </li></ul><ul><li>Sprint Reviews </li></ul><ul><li>Retrospectives </li></ul>
  9. 9. Project success through empowered Teams <ul><li>Scrum is about personal accountability and empowerment. The team members who embrace the concept and participate in and accept team commitments [i ] are: </li></ul><ul><li>Self Disciplined: Project teams without self-discipline will, in the end, be lazy and careless (I see it all too often), or fall back upon externally imposed discipline, a notoriously weak form of discipline. </li></ul><ul><li>Self Organized: A particular form of esprit de corps and initiative develops when the people on the project choose their own leaders, their own tasks, their own peer-operating rules. They tend to be more fervent about the quality of their work, their code of conduct. Many a project has been saved because the technical people banded together to make sure they delivered their product despite the hierarchy they reported to. </li></ul><ul><li>Self Aware: The team becomes self-aware, when it is able to discuss about how they are and how they might get better, what their responsibilities are to each other and to themselves. </li></ul><ul><li>[i] Self-Awareness: An Overlooked Key to Agility, Alistair Cockburn, February 9, 2009, Gantthead. </li></ul><ul><li>iv 5Q's on Agile with Arlen Bankston, by Arlen Bankston, May 28, 2008, ibid, i. </li></ul>
  10. 10. Scrum promotes IT success: <ul><li>Scrum works through empowerment: </li></ul><ul><ul><li>Team Ownership and Commitment </li></ul></ul><ul><ul><li>Scrum requires an organizational change how management thinks about itself in terms of IT’s role in the business. </li></ul></ul><ul><ul><li>Benefits to the IT organization: </li></ul></ul><ul><ul><li>Scrum will highlights impediments to delivering business solutions </li></ul></ul><ul><ul><li>Helps the organization in identify and remove barriers inhibiting project success </li></ul></ul><ul><ul><li>Help IT figure out how to deliver faster better solutions to meet your business’ customers speed to market demands. </li></ul></ul>
  11. 11. Questions and Answers <ul><li>Please send any questions, discussions, or comments to: </li></ul><ul><ul><li>Dave Rognerud at [email_address] </li></ul></ul><ul><ul><li>Or email for an appointment to discuss your project needs. </li></ul></ul>
  12. 12. THANK YOU

×