Overview of Scrum Scrum is the most popular Agile framework. It is an adaptive, iterative, fast, flexible, and effective method designed to deliver significant value quickly and throughout a project. Scrum ensures transparency in communication and creates an environment of collective accountability and continuous progress. The Scrum framework, as defined in the SBOK Guide, is structured in such a way that it supports product and service development in all types of industries and in any type of project, irrespective of its complexity. A Scrum project involves a collaborative effort to create a new product, service, or other result as defined in the Project Vision Statement. Projects are impacted by constraints of time, cost, scope, quality, resources, organizational capabilities, and other limitations that make them difficult to plan, execute, manage, and ultimately succeed. However, successful implementation of the results of a finished project provides significant business benefits to an organization. It is therefore important for organizations to select and practice an appropriate project delivery approch. A key strength of Scrum lies in its use of cross-functional, self-organized, and empowered teams who divide and execute their work in short, concentrated work cycles called Sprints. The focus of Scrum on value-driven delivery helps Scrum Teams deliver results as early in the project as possible. Release Planning Schedule Daily Standup Create Deliverables Project Business Case Project Vision Statement Prioritized Product Backlog Sprint Backlog Accepted Deliverables Scrum Flow for one Sprint
Google Trends Analysis: Scrum is more popular than PMP or PRINCE2 United States 2004 - present Jobs & Education Web Search Compare Search terms Scrum Search term PMP Search term PRINCE2 Search term + Add terms Interest over time Average 2005 2007 2009 2011 2013 How to generate this graph? Step 1: Visit www.google.com/trends Step 2: Compare Scrum, PMP, and PRINCE2 Step 3: From the top menu, change the Country to United States and the Category to Jobs & Education PRINCE2 is a registered trademark of AXELOS Limited. PMP is a registered trademark of Project Management Institute, Inc.
Scrum vs. Traditional Project Management Differences between Scrum and traditional project management models Scrum Traditional Project Management Emphasis On people On processes Documentation Minimal only as required Comprehensive Process style Iterative Linear Upfront planning Low High Prioritization of requirements Based on business value and are regularly updated Fixed to the Project Plan Quality assurance Customer-centric Process-centric Organization Self-organized Managed Management style Decentralized Centralized Change Updates to Prioritized Product Backlog Formal Change Management System Leadership Collaborative, Servant Leadership Command and control Performance measurement Business value Plan conformity Return on Investment (ROI) Early, throughout project life End of project life Customer involvement High, throughout the project Varies, depending on the project lifecycle
Scrum Process Chart AEC Scrum Principles Diagram Initiate Plan & Estimate Implement Review & Retrospect Process style Create Project Vision Create User Stories Create Deliverables Convene Scrum of Scrums Ship Deliverables Identify Approve, Estimate Conduct Daily Demonstrate and Retrospect Project Scrum Master & and Commit Standup Validate Sprint Stakeholder(s) User Stories Form Scrum Team Create Tasks Groom Prioritized product Backlog Retrospect Sprint Develop Epics(s) Estimate Tasks Create Prioritized Product Backlog
Scrum Process Chart Scrum Plan & Principles Estimate Roles : Cores $ $ $ $ $ $ $ $ $ $ $ $ $ Initiate Empirical Process Control Scrum prescribes making decisions based on observation and experimentation rather than detailed upfront planning. Self-Organization Scrum believes that today s workers have much more knowledge to offer than just their technical expertise and that they deliver greater value when self-organized. Collaboration In Scrum, product development is a shared value-creation process that needs all the stakeholders working and interacting together to deliver the greatest value. Value-based Prioritization Delivering the greatest value in the shortest amount of time requires prioritization and selection of what could be done from what should be done. Time-boxing Time is treated as a limiting constraint and time-boxing is used as the rhythm to which all stakeholders work and contribute. Iterative Development The customer may not always be able to define very concrete requirements. The iterative model is more flexible in accommodating changing requirements. Product Owner Defines the Project Vision and Release Schedule as the Voice of the Customer Defines customer requirements in the form of Epics/User Stories and clarifies these requirements for team members Prioritizes items on the Product Backlog according to business value Provides Acceptance/Done Criteria and inspects deliverable(s) to validate them Scrum Master Ensures that Scrum processes are correctly followed by all Scrum Core Team members, including the Product Owner Ensures that an ideal project environment exists for the Scrum Team to successfully complete Sprints Oversees Release Planning Sessions and convenes other meetings Acts as a servant-leader that helps motivate and coach the team Scrum Team Typically a small team of 6 10 members with no further subdivision of teams Cross-functional and self-organizing, the Scrum Team enjoys complete autonomy during a Sprint Members are generalists across domains and specialists in at least one area Responsibility for the work lies with the Non-Cores Stakeholders Customers Users Sponsors Vendors Scrum Guidance Body
6.00 5.00 4.00 3.00 2.00 1.00 Scrum Process Chart Artifacts Plan & Estimate Meetings Project Vision Statement Project Vision Meeting A the business need the project is intended This meeting explains the business needs to meet and should focus on the problem the project is intended to meet and rather than the solution. should focus on the problem rather than 1 2 Prioritized Product Backlog the solution. 3 4 The Product Owner generates a prioritized Release Planning Meeting list of requirements that, when turned into The purpose of this meeting it to develop potentially shippable product functionality, a Release Plan that defines when various will deliver the Project Vision. Owned by the sets of usable functionality or products Product Owner. will be delivered to the customer. Sprint Goal Sprint Planning Meeting Proposed by the Product Owner and The primary output of this meeting is the accepted by the team, it is a one-sentence Sprint Backlog. Task Planning and Task aim for the current Sprint. Estimation are accomplished during Sprint Backlog A the Scrum Team commits to executing Sprint Planning. Time-boxed to 8 hours for a 1-month Sprint. this list of items in the upcoming Sprint. Any 3 2 1 Daily Standup Meeting risk-mitigating activities are also included as Scrum Team members gather for short, tasks in the Sprint Backlog. daily meeting time-boxed to 15 minutes. Initiate $ Impediment Log Impediments or obstacles encountered by the team should be formally recorded by the Scrum Master in an Impediment Log. Product Increment The potentially shippable deliverable of the team at the end of each Sprint that satisfies the Acceptance and Done Criteria. Retrospect Sprint Meeting Team members discuss what went well during the previous Sprint and what did not go well, the goal being to learn and make Each Scrum Team member answers the following three questions: What did I do yesterday? What will I do today? What s in my way? Sprint Review Meeting The Scrum Team presents the completed Sprint deliverables to the Product Owner who either accepts or rejects them based on the defined Acceptance and Done Criteria. Time-boxed to 4 hours for a 1-month Sprint. improvements in the Sprints to follow. Time-boxed to 4 hours for a 1-month Sprint.
Why Use Scrum? Some of the key benefits of using Scrum Adaptability Empirical process control and iterative delivery make projects adaptable and open to incorporating change. Transparency All information radiators such as Scrumboards and Sprint Burndown Charts are shared, leading to an open work environment. Continuous Feedback Continuous feedback is provided through the Conduct Daily Standup and Demonstrate and Validate Sprint processes. Continuous Improvement The deliverables are improved progressively in each Sprint, through the Groom Prioritized Product Backlog process. Faster Problem Resolution Problems are resolved quickly due to collaboration between cross functional teams. Efficient Development Process The development process is efficient due to time-boxing and minimization of nonessential work. Sustainable Pace Scrum processes are designed such that the people involved can work at a sustainable pace that they can, in theory, continue indefinitely. Early Delivery of High Value The Create Prioritized Product Backlog process ensures that the highest value requirements of the customer are satisfied first. Effective Deliverables The Create Prioritized Product Backlog process and regular reviews after creating deliverables ensure effective deliverables to the customer. Customer-centric Emphasis on business value and an collaborative approach to stakeholders ensure a customer-oriented framework period. High Trust Environment The Conduct Daily Standup and Retrospect Sprint processes promote transparency and collaboration, leading to low friction among employees. Collective Ownership The Approve, Estimate, and Commit User Stories process allows team members to take ownership of the project and their work, leading to better quality. Continuous Delivery of Value Iterative processes enable the continuous delivery of value through the Ship Deliverables process as frequently as the customer requires. High Velocity A collaborative framework enables highly skilled cross-functional teams to achieve their full potential and high velocity. Innovative Environment The Retrospect Sprint and Retrospect Project processes create an environment of introspection and learning, leading to innovation and creativity. Motivation The Conduct Daily Standup and Retrospect Sprint processes lead to greater levels of motivation among employees.
Why SCRUMstudy? 11 reasons why SCRUMstudy is the best Scrum accreditation body Parameters SCRUMstudy Scrum/Agile Certifications 1. Most popular and widely accepted VMEdu has trained more than 400,000 students in delivering successful projects More than 5,000 students certified each month for Scrum/Agile Largest partner network of 275+ Authorized Training Partners (A.T.P.s) 2. Based on Scrum Body of Knowledge (SBOK Guide) All exams are based on A Guide to the Scrum Body of Knowledge (SBOK Guide) This guide is the definitive and detailed industry guide endorsed by Scrum experts 3. Industry-wide acceptance Applied by organizations in diverse projects spanning an eclectic mix of industries 4. Scalable Scrum Enables practitioners to scale Scrum to the Portfolio and Program levels, aligned to the way organizations work 5. Established name in Scrum/Agile certifications Widest network of A.T.P.s globally offering its certifications Widely reputed and accepted by various Fortune 500 companies such as Apple, IBM, HP, Bank of America, AT&T, Dell, Verizon, Lockheed Martin, and PepsiCo 6. Active discussions to share and learn Active discussions on LinkedIn, Twitter, Facebook, Google+, and more discussion forums and blogs Most active Group for Scrum on LinkedIn https://www.linkedin.com/groups/scrumstudy-1-group-scrum-agile-6718717 7. Multiple free resources for Scrum & Agile Community Wide range of free resources such as 5+ hours of high-quality videos, useful case studies, interactive mobile apps, blogs, and articles 8. Free "Scrum Fundamentals Certified" - SFC Course Free certification includes approximately 10 hours of free online self-study through videos, case studies, and guides 9. Credible and standard testing environment Certification exams conducted using live online proctoring system to maintain the integrity of the exams 10. Teaching methodology Scientifically proven and highly interactive teaching methodology including role-plays, case studies, and simulations 11. Experienced SCRUMstudy trainers SCRUMstudy Certified Trainers (SCT ) undergo a rigorous assessment process and are required to successfully pass three SCRUMstudy certification exams before they are eligible to teach
Certification Hierarchy AEC This Certification Hierarchy Diagram shows the preferred and optional certification needed to move to the next level. SFC (free introductory online course for anyone interested in learning about Scrum) SDC (for all Scrum Team Members, Participants, and Stakeholders) SMC (for all Scrum Masters) SPOC (for all Scrum Product Owners) AEC (general Agile certification for Agile professionals) Optional but preferred Mandatory ESMC (Expert Scrum Master Certified) Certification Hierarchy SCRUMstudy certified professionals help organizations with improved levels of project delivery that leads to increased returns on investment for projects.
Scrum Fundamentals Certified (SFC ) SFC Scrum Fundamentals Certified' course is tailored to help anyone interested to know more about Scrum ; learn about key concepts in Scrum as defined in the SBOK Guide; and to get a basic understanding of how Scrum framework works in delivering successful projects. This course is included as a part of Free Primary Lifetime Membership. The purpose of the 'Scrum Fundamentals Certified' exam is to confirm you have basic understanding of the Scrum framework. On passing the exam, you will be accredited as "Scrum Fundamentals Certified". You will also be provided with 10 PMI approved PDUs. Syllabus 1. Introduction to Scrum Scrum Overview Scrum Principles, Aspects and Processes Examination Format Multiple choice 75 questions per exam No negative marks for wrong answers 90 minutes duration Proctored online exam Current pass rate: 98% Prerequisites There is no formal prerequisite for this certification. However, SDC or SMC Certified professionals will be able to better understand the concepts required for this certification exam. Maintaining Certification (RCUs) not applicable Audience Profile Anyone interested in knowing more about Scrum can take up this course and exam for free.
Scrum Developer Certified (SDC ) SDC Scrum Developer Certified (SDC ) is an entry-level certification for Scrum Team members and those who interact with any Scrum Team. The objective of this certification is to ensure that students understand the basics of Scrum that Scrum Team members need to know in order to effectively contribute to a Scrum project. On successful completion of the course, students will be able to apply Scrum effectively as Scrum Team members in Scrum/Agile projects. Syllabus 1. Introduction to Scrum Scrum Overview Scrum Principles, Aspects and Processes 2. Organization Core roles and Non-core Roles 3. Business Justification Value-driven Delivery Factors used to Determine Business Justification Confirm Benefits Realization 4. Quality Quality Defined Quality, Scope and Business Value Quality Management in Scrum 5. Change Unapproved and Approved Changes Change in Scrum 6. Risk Risks and Issues Risk Management Procedure 7. Introduction to Scrum Project Phases Form Scrum Team and Develop Epics processes Create Prioritized Product Backlog and Conduct Release Planning Processes 9. Plan and Estimate Create User Stories Process Approve, Estimate, and Commit User Stories Process Create Tasks and Estimate Tasks Processes Create Sprint Backlog Process 10. Implement Create Deliverables and Conduct Daily Stand-up processes Groom Prioritized Product Backlog Process 11. Review and Retrospect Convene Scrum of Scrums Process Demonstrate and Validate Sprint Process Retrospect Sprint Process 12. Release Ship Deliverables and Retrospect Project Processes Examination Format Multiple choice 75 questions One mark awarded for every right answer No negative marks for wrong answers 90 minutes duration Proctored online exam Prerequisites There is no formal prerequisite for this certification. Maintaining Certification - Re-cerification Units (RCUs) 25 RCUs every 3 years. Audience Profile This is highly recommended for everyone in a company who works in a Scrum Team, interacts with any Scrum Team, or is interested in understanding the basics of Scrum and how this method could be used effectively. 8. Initiate Create Project Vision Process Identify Scrum Master and Stakeholders Process 13. Scaling of Scrum Scalability of Scrum and Mapping Traditional Roles to Scrum
Scrum Master Certified (SMC ) SMC Scrum Master Certified (SMC ) is a certification for Scrum Masters and experienced practitioners needing or wanting more advanced instruction. The objective of this certification is to confirm that the applicants have achieved sufficient understanding of how to apply Scrum in projects, and how to tailor Scrum to a particular scenario. Examination Format Multiple choice Syllabus 1. Agile Overview The Rise of Agile The Agile Manifesto Principles the of Agile Manifesto Declaration of Interdependence Agile Methods Agile vs. Traditional Project Management 2. Scrum Overview Scrum Principles Scrum Aspects Scrum Processes Scrum Advantages 3. Scrum Roles Core Roles i. Product Owner ii. Scrum Master iii.scrum Team e. Release f. Input, Tools and Outputs for Non-core Roles 4. Scrum Phases Initiate Plan and Estimate Implement Review and Retrospect Release 5. Scaling Scrum Scalability of Scrum Scrum in Programs and Portfolios Scrum of Scrums (SoS) Meeting Transition to Scrum Mapping Traditional Roles to Scrum Maintaining Stakeholder Involvement Importance of Executive Support 100 questions One mark awarded for every right answer No negative marks for wrong answers 120 minutes duration Proctored online exam Prerequisites Preferably SDC certified. Maintaining Certification - Recertification Units (RCUs) 40 RCUs. Audience Profile This certification is appropriate for anyone who is interested in working as a Scrum Master, or who is already a Scrum Master in his/her organization.
Scrum Product Owner Certified (SPOC ) SPOC Scrum Product Owner Certified (SPOC ) is a certification for Product Owners and experienced practitioners who represent the business interests in a project. The Scrum Product Owner Certified (SPOC ) certification is designed to confirm the applicants' practical knowledge of Scrum that equips them to understand the business aspects and interact with multiple stakeholders in a Scrum environment. Examination Format Multiple choice 140 questions Syllabus 1. Agile Overview What is Agile? and Why use Agile? The Agile Manifesto and its Principles Declaration of Interdependence Agile vs. Traditional Project Management Agile Methods 2. Scrum Overview Planning in Scrum Scrum Framework Scrum Roles Scrum Flow 3. Initiate Create Project Vision Identify Scrum Master and Stakeholders Form Scrum Team Develop Epics Create Prioritized Product Backlog Conduct Release Planning 4. Plan and Estimate Create User Stories Approve, Estimate, and Commit User Stories Create Tasks Estimate Tasks Create Sprint Backlog 5. Implement Create Deliverables Conduct Daily Stand-up Groom Prioritized Product Backlog 6. Review and Retrospect Convene Scrum of Scrums Demonstrate and Validate Sprint Retrospect Sprint 7. Release Release Ship Deliverables Retrospect Project One mark awarded for every right answer No negative marks for wrong answers 180 minutes duration Proctored online exam Prerequisites There is no formal prerequisite for this certification. However, SDC or SMC certified professionals will be able to better understand the concepts required for this certification exam. Maintaining Certification - Re-cerification Units (RCUs) 40 RCUs every 3 years. Audience Profile This is highly recommended for anyone in a company who interacts with a Scrum Team, provides business requirements or manages business aspects of a project.
Agile Expert Certified (AEC ) AEC Agile Expert Certified (AEC ) professionals possess a wide-ranging knowledge and understanding of the values, methods and intricacies of Agile. The objective of this certification is to ensure that applicants have the ability to compare and choose the appropriate methodology in a given situation. Syllabus 1. Introduction c. Practices of Lean Software 2. Test-Driven Development Development d. Iterative Development 3. Agile Overview a. AGILE Defined 7. Understanding Kanban b. Why use Agile? a. Kanban in Software c. Adaptive Project Management Development d. The Agile Manifesto b. Kanban Values e. Principles of the Agile Manifesto c. Kanban Practices f. Declaration of Interdependence d. Definition of Lean Kanban g. What has changed? e. Implementing Lean Kanban h. Difference between Waterfall and 8. Domains of Agile Practices Agile a. Value-Driven Delivery 4. Scrum Overview b. Adaptive Planning a. Overview of Scrum c. Team Performance Practices b. Brief History of Scrum d. Agile Tools and Artifacts c. Why Use Scrum? e. Participatory Decision Models d. Scalability of Scrum f. Stakeholder Engagement e. Scrum Principles g. Continuous Improvement f. Scrum Aspects 9. Crystal g. Scrum Processes a. Core Values h. Scrum and Kanban b. Coles 5. Lean Kanban Software c. Practices Development d. The Process a. Introduction 10. DSDM b. Core Values a. Core Values 6. Understanding Lean Software b. Coles Development c. Practices a. Introduction 11. Best Fit Analysis Tool b. Core Values 12. Comparison of Agile Methods Examination Format Multiple choice 100 questions per exam One mark awarded for every right answer No negative marks for wrong answers 120 minutes duration Proctored online exam Current Pass Rate: 95% Prerequisites There is no formal prerequisite for this certification. However, SDC or SMC Certified professionals will be able to better understand the concepts required for this certification exam. Maintaining Certification (RCUs) 40 Recertification units every 2 years Audience Profile This certification is appropriate for anyone who is interested in working as a Scrum Master or for someone who is already a Scrum Master in an organization.