Scrum Basics for Auditors: Enhancing Project Management Efficiency

Slide Note
Embed
Share

Explore the fundamentals of Scrum methodology tailored for auditors, enabling impactful teamwork, accountability, and transparency. Discover key terminology, roles, and processes to streamline project management and achieve audit objectives effectively.


Uploaded on Oct 02, 2024 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript


  1. PROJECT MANAGEMENT FOR AUDITORS Scrum 1

  2. WHY SCRUM? Impact Teamwork Efficient Accountable Transparent Nimble 2

  3. WHATIS SCRUM? 3

  4. TRADITIONAL PROJECT MANAGEMENT VS. SCRUM Constrained by: Scope Cost Schedule Impact Driven Plan Driven Estimate: Cost Schedule Scope Source: Michele Sliger, Stickyminds.com 4

  5. ESSENTIAL SCRUM TERMINOLOGY Potentially shippable product = Final, not draft product. Product Backlog = Tasks to complete audit objectives Sprint Backlog = To-do list for the sprint. Sprint = Iteration in which the Scrum Team concentrates on achieving goals defined in the current sprint backlog. 24 hours 2-3 weeks Potentially shippable product 5 Sprint Product Backlog Sprint Backlog

  6. SCRUM ROLES Product Owner = Develops and prioritizes the Product backlog. Scrum Team = Workforce to complete backlog items Scrum Master = Team leader 6

  7. Product Backlog SPRINT PLANNING: PRODUCT OWNER Product Owners and Team: Prioritize product backlog Set the sprint goal Identify user stories Define done 7

  8. Sprint Backlog SPRINT PLANNING: SCRUM TEAM Identify items from product backlog Break into 0-4 hour tasks Estimate time Prioritize 8

  9. Sprint Backlog SPRINT PLANNING: SCRUM TEAM 9

  10. Sprint Backlog SPRINT PLANNING: SCRUM TEAM 10

  11. 2-3 wks Sprint THE BURNDOWN CHART Pending 80 In Progress 70 60 50 Complete Task Hours 40 30 Remaining 20 10 Effort 0 Sprint Days 11 Linear (Remaining)

  12. 24 hrs Daily Scrum IN 15 MINUTESORLESS: DAILYSCRUM What did you do yesterday? What will you do today? Any impediments? 12

  13. Potentially Shippable Product SPRINT REVIEW Present the potentially shippable product. This could include: Workpaper for internal QA or auditee technical review Detailed audit plan to supervisor Report chapter for editing or auditee technical review 13

  14. SPRINT RETROSPECTIVE Attended only by the team What went well What could we do differently 14

  15. ESSENTIAL SCRUM TERMINOLOGY: REVIEW 24 hours 2-3 weeks Potentially shippable product Sprint Product Backlog Sprint Backlog 15

  16. WHATKINDOFPROJECTSWORKWELL WITH SCRUM? Project with complexity and ambiguity Project in which dependencies can be minimized Project with interested stakeholders and high-value outcomes 16

  17. WHATKINDOFTEAMSWORKBESTWITH SCRUM? Teams who enjoy a self-directed, collaborative approach to a project Preferably co-located Teams who value accountability to one another Teams who have the authority to do what is needed to meet sprint commitments 17

  18. QUESTIONS? Kymber Waltmunson, CIA, CGAP, CSM, MPA, MA King County Auditor s Office kymber.waltmunson@kingcounty.gov 206-296-0383 18

More Related Content