This document provides an overview of Agile and Scrum frameworks. It discusses the Agile Manifesto and 12 principles, Scrum roles like Product Owner and Scrum Master, Scrum artifacts like Product Backlog and Sprint Backlog, and Scrum ceremonies like Sprint Planning, Daily Standup, Sprint Review and Retrospectives. The goal of Scrum is to deliver working software frequently through an empirical and iterative process that is transparent, inspectable and adaptable.
This document provides an introduction to agile project management. It begins by contrasting traditional project management, which relies on upfront planning, with agile project management, which uses iterative development cycles. The key principles of agile project management are then outlined, including a focus on customer value, iterative and incremental delivery, experimentation and adaptation, self-organization, and continuous improvement. Popular agile methods like Scrum, Extreme Programming, and others are briefly described. The remainder of the document focuses on how the Scrum methodology works in practice and some of the challenges of applying agile principles to large projects.
Quality Assurance Comparison in Traditional and Agile Methodologiescoolbreeze130
This document compares quality assurance techniques between traditional and agile software development methodologies. It discusses the limitations of traditional waterfall models and agile methods. Traditional methods emphasize well-defined requirements and documentation, while agile prioritizes working software through short iterations with frequent customer feedback. Both approaches aim to ensure quality, but agile relies more on practices like refactoring, test-driven development, and continuous integration throughout the development cycle. In conclusion, agile may better facilitate quality by starting testing earlier and more frequently integrating customer input.
This document provides an overview of Agile methodology. It defines Agile as an iterative software development practice that emphasizes continuous testing and collaboration over rigid processes. The key points covered include:
- The core values of Agile focus on interactions, working software, customer collaboration, and responding to change.
- Agile uses incremental and iterative development compared to the sequential waterfall model. This allows for early customer feedback and flexibility.
- Benefits of Agile include adapting to changes, delivering working software frequently, engaging stakeholders, and improving quality.
- Common roles in Agile include the Scrum Master, team members, Product Owner, and stakeholders. The Scrum Master facilitates the team while the Product Owner prior
The document discusses Agile software development methodology compared to traditional methods. Agile methodology uses shorter iterative development cycles called sprints to frequently deliver working software, whereas traditional methods follow sequential phases. An example project to develop a word processor shows how requirements gathering, design, coding, testing would be broken into 10 sprints in Agile vs sequential phases over 10 months in traditional methods. Agile allows for more collaboration, adaptation to changes, and earlier return on investment compared to traditional plan-driven methods.
This power point presentation is an introduction to Scrum and covers the following topics:
* Problems with a traditional approach
* What is Scrum?
* Why use Scrum?
* How does Scrum work?
* The Product Owner
* The Scrum Master
* The Team
* The Product Backlog
* Benefits of using a Product Backlog
* The Sprint Backlog
* The Scrum Cycle
* The Burn Down Chart
You can copy, distribute, and use the content of the presentation in accordance to Creative Commons Attribution 2.5 License.
A high-level introduction on agile development methods. Going over some concepts, used terminology and a couple of slides specifically on SCRUM and Kanban.
The document discusses Agile project management and Scrum frameworks. It describes Agile as a collection of values and principles for software development that emphasize individuals, working software, customer collaboration, and responding to change. Scrum is presented as a framework that uses short iterations called sprints, daily stand-up meetings, and emphasizes self-organizing cross-functional teams to deliver working software increments for customer feedback. Effective Scrum teams are autonomous, strive for continuous improvement, and have members with diverse skills who collaborate well.
The document describes an agile development method that focuses on having a unified team work on the highest priority tasks. It discusses foundations of the method including backlog grooming, velocity-based work capacity, and priority-based work allocation and focus. It then describes the iterative development method including sprint planning, execution, and retrospectives. It emphasizes evolving the method through retrospectives and periodic assessments to balance change and stability.
The document provides an introduction to Agile principles and practices. It discusses that Agile focuses on customer collaboration and delivering working software frequently. It describes the creation of the Agile Alliance by 17 software developers who wrote the Agile Manifesto emphasizing individuals, interactions, working software, and responding to change. It also outlines 12 Agile principles and compares traditional waterfall and Agile rapid development methods.
The document describes AGILIX's 5D methodology for strategic partnerships with clients. The 5 phases are: D1 Define, D2 Discover, D3 Design, D4 Develop, and D5 Deploy. In D1, requirements are gathered from subject matter experts. D2 focuses on design options and prototypes. In D3, development begins using a pattern library. D4 consists of sprints to build functionality. D5 involves testing and piloting before full deployment. The methodology aims to keep requirements high-level initially for agility, gather user feedback, and accommodate new needs through iteration.
Planon switched to the SCRUM development method in 2004 to address issues with their previous Prince2 method. This allowed for biannual releases with marketing versions in between, and made changes more affordable to implement. Under SCRUM, teams self-select tasks for one month sprints. Product quality is ensured through effective team composition, test automation, and test effort estimation per backlog item. The agile product management process at Planon starts by identifying business problems and acquiring stakeholder input to determine themes and functionality to implement, estimating costs and opportunities. Themes are broken into concepts and solution stories to define requirements assigned to SCRUM teams.
This document discusses the challenges of managing localization for 31 languages simultaneously with each software sprint release. It describes the localization team's transition from a waterfall model to an agile "Locban" methodology, which is a localized adaptation of the Kanban methodology. Locban uses visualization tools to increase transparency and support the localization processes of planning, execution, monitoring, and closure for each sprint. This approach helped improve productivity by allowing the team to certify features across all languages within each short, one-month sprint timeline.
Ray Business Technologies Process Methodologyray biztech
This document describes the process methodology used by Ray Business Technologies for IT project deliveries. It involves a 4D delivery process of discover, define, develop and deploy phases. Key aspects include iterative development with deliverables in each phase. The methodology is modeled after agile principles and includes roles like project manager, architect and developers. Typical project deliverables and change management process are also outlined. The company provides IT solutions and services from its locations in India, US and UK.
The document discusses agile project management and compares it to the traditional approach. It outlines the key phases and characteristics of the Scrum framework, an agile method for managing iterative development projects. Scrum uses short "sprints" to iteratively develop software in increments, with daily stand-ups and involvement from customers and stakeholders. At the end of each sprint, completed work is reviewed and new work is planned for the next sprint. Scrum provides flexibility to adapt the project as requirements change compared to the traditional sequential approach.
A software testing practice that follow the principle of agile software development is called Agile Testing.
Agile is an iterative development methodology where requirement evolve through collaboration between the customer and self-organizing teams and agile aligns development with customer need.
Website: https://www.1solutions.biz/
This document discusses agile project management. It defines agile management as an iterative development model where deliverables are submitted in stages. The key principles of agile management are outlined, including valuing individuals, customer collaboration, responding to change, and simplicity. Several agile methods are described such as scrum, extreme programming, and lean software development. Criticisms of the agile approach are mentioned along with the concept of "post-agilism," which advocates a flexible approach rather than strict adherence to agile dogma. The document concludes with advice for project managers to consider factors like developer skills, requirements, organizational culture, project criticality, and team size when determining a project management approach.
This document discusses best practices for adopting agile methodologies in fixed-bid projects. It identifies key challenges such as lack of mutual trust between customers and vendors and lack of customer involvement. It recommends holding a pre-game workshop to establish product vision, estimate scope and timeline, and agree on ways of working. It also recommends collaborative change management where customers can change low priority stories without cost. These practices help deliver projects on time and within budget while allowing flexibility that agile requires.
This document describes the Scaled Agile Framework (SAFe) which is a framework for implementing agile development practices at the enterprise level. It discusses how SAFe addresses the limitations of traditional waterfall development and scales agile to meet the needs of large projects. SAFe incorporates key lean principles and consists of three levels - Team, Program, and Portfolio. At each level it defines roles and practices for planning, prioritizing work, and delivering value in short iterations. The goal of SAFe is to synchronize collaboration across many agile teams to continuously and predictably deliver working software.
The document discusses principles for being agile and delighting customers. It suggests companies should be ready for the unpredictable like Oreo, adapt and innovate like Fujifilm, frequently deliver products like Zara, and care about customers like Zappos. It also emphasizes focusing on people and culture like Zappos. To create an agile culture, the document recommends establishing autonomous teams that iteratively deliver frequently, getting customer feedback to continuously improve processes and letting this new way of working spread throughout the company.
The document summarizes Mike Cohn's presentation on user stories at the Norwegian Developer's Conference. It discusses that user stories address the communication problem between stakeholders who want software and developers who build it. It also notes that user stories allow for a balanced approach and shared responsibility over resource allocation. User stories support iterative development and conversations between stakeholders and developers.
Douglas Talbot & Sandy Mamoli
One of the most fundamental problems facing a project is how you decide on, document, and manage your requirements.
Obviously Agile software development promotes handling this very differently than a Waterfall approach. One mechanism used by Agile projects to track requirements is the "User Story" - but what are they, how are they created, who uses them, when and how, within the development cycle?
The document discusses user stories, which are short descriptions of customer-valued functionality written in the form of "As a [type of user], I want [goal] so that [benefit]". User stories help define requirements, facilitate planning and tracking progress, and validate completed work. They should be independent, negotiable, valuable, estimable, small, and testable. The document provides guidelines for writing effective user stories and splitting large stories into smaller pieces.
Introduction To User Stories For Agile Product Developmentzenpdm
The document discusses user stories, which describe functionality or features a product will deliver to users. It explains that a user story should have an independent central character and plot, with a clear outcome. The document outlines best practices for writing user stories according to the INVEST criteria - ensuring stories are independent, negotiable, valuable, estimable, small, and testable. It concludes by inviting the reader to a workshop to further discuss techniques for identifying user stories.
Compared to traditional software engineering, agile development is mainly targeted at projects with dynamic, undeterministic and non-linear characteristics, where accurate estimates, stable plans and predictions are often hard to get in early stages, and big up-front designs and arrangements will probably cause a lot of waste, i.e. are not economically sound.
Agile software development is a group of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, continuous improvement and encourages rapid and flexible response to change. It is a conceptual framework that focuses on frequently delivering small increments of working software.
Incorporating Learning and Expected Cost of ChangeMike Cohn
This document presents three guidelines for prioritizing features on agile projects:
1. Defer features with high expected costs of change, which is the probability of change multiplied by the cost of change. Features likely or costly to change should be delayed.
2. Prioritize features that generate useful knowledge, such as knowledge about a feature's desirability, usability, or technical feasibility.
3. Incorporate new learning often to decide what to do next, either implementing a feature now or reevaluating it later. Priorities should be reassessed each iteration to acknowledge continuous learning.
This presentation by certified Scrum trainer Mike Cohn addresses a common challenge in agile development: the new role of leaders and managers in self-organizing teams.
This document discusses project selection and prioritization. It covers various financial metrics used to evaluate projects including net present value (NPV), internal rate of return (IRR), payback period, and modeling project returns and costs. An example of evaluating a proposed new feature for a web-based payroll system called WebPayroll is presented, with financial projections built out over 8 quarters to calculate the NPV, IRR, payback period and discounted payback period for the project. The document emphasizes the importance of estimating project costs in addition to modeling projected financial returns in order to properly evaluate and prioritize projects.
STC Toronto Agile Intro - How can this possibly work?Michael Sahota
This is an invited talk I gave at STC Management Day in Toronto (Feb 2010). After intro, show role of docs in iterations - sometimes trailing.
Let me know if you would like a copy of this presentation for your own use
This document discusses transitioning to an agile development process and overcoming challenges associated with previous waterfall methods. It provides a framework for transitioning that includes treating the transition as a project with its own backlog and iterations. Common "waterfallacies" and fears of change ("agilephobias") are addressed, such as the inability to accurately predict schedules and fixed requirements upfront. Distributed teams and integrating testing are also discussed. The transition process itself needs to be agile and adapt to challenges identified along the way.
Getting Agile with Scrum discusses Scrum, an agile framework for project management. Some key points:
- Scrum uses short "sprints" typically 2-4 weeks long where work is designed, coded, and tested simultaneously rather than sequentially passed between teams.
- Scrum roles include the Product Owner who prioritizes work, the Scrum Master who facilitates the process, and a cross-functional Team.
- Ceremonies like daily stand-ups, sprint planning and reviews, and retrospectives help manage the work and process.
- Burndown charts track work completion. Scaling can involve multiple Scrum teams working on the same product managed through communities of practice.
The document discusses problems with traditional software development approaches and how agile software development aims to address these problems. Specifically, it notes that traditional phased development often results in unclear requirements, requirements that change and become more expensive to change, projects that take too long, lack of testing, and wasted time on unused functionality. Agile development breaks projects into shorter iterations to allow for inspection and adaptation, improving visibility, catching failures earlier, and focusing on only the most valuable functionality.
This document discusses planning and tracking agile projects. It begins by introducing Mike Cohn and his background. It then provides examples for estimating tasks using story points and planning poker. It discusses relating different planning levels from portfolio down to daily tasks. Release planning and using velocity and a prioritized backlog to estimate delivery dates is covered. Finally, it discusses using burndown charts to track progress at both the iteration and release levels.
Velocity is perhaps the most useful metric available to agile teams. In this session we will look at advanced uses of velocity for planning under special but common circumstances. We will see how to forecast velocity in the complete absence of any historical data. We will look at how a new team can forecast velocity by looking at other teams. We will see how to predict the velocity of a team that will grow or shrink in size. Most importantly we will look at the use of confidence intervals to create plans we can be 90% confident in, even on fixed-price or fixed-date contracts.
The first step in creating a useful plan is the ability to estimate reliably. In this session we will discuss how to do this. We will look at various approaches to estimating including unit-less points and ideal time. The class will present four specific techniques for deriving reliable estimates, including how to use the popular Planning Poker® technique and other techniques that dramatically improve a project's chances of on-time completion.
The technique of expressing requirements as user stories is one of the most broadly applicable techniques introduced by the agile processes. User stories are an effective approach on all time constrained projects and are a great way to begin introducing a bit of agility to your projects.
In this session, we will look at how to identify and write good user stories. The class will describe the six attributes that good stories should exhibit and present thirteen guidelines for writing better stories. We will explore how user role modeling can help when gathering a project’s initial stories.
Because requirements touch all job functions on a development project, this tutorial will be equally suited for analysts, customers, testers, programmers, managers, or anyone involved in a software development project. By the end of this tutorial, you will leave knowing the six attributes of a good story, learn a good format for writing most user stories, learn practical techniques for gathering user stories, know how much work to do up-front and how much to do just-in-time.
A brief and visual introduction to the Agile.
Learn the Agile mindset and the big 3 (Extreme Programming, Scrum, and Kanban). Be able to whiteboard a simple view of how each one works to get things done and make things happen.
Scaling Agile and Working with a Distributed TeamMike Cohn
Mike Cohn presented on scaling agile with distributed teams. Some key challenges in scaling agile include managing dependencies between teams, coordinating large iteration planning meetings, and coordinating multiple teams. To address these challenges, Cohn recommends proactively managing dependencies, using rolling lookahead planning, scaling up iteration planning meetings by staggering them over multiple days or using a "big room" approach, and establishing communities of practice to facilitate collaboration. When teams are distributed across locations, it is important to decide how work will be distributed, create coherence among team members, and change communication approaches, such as adding documentation, encouraging lateral communication, and addressing time zone differences.
The first step in creating a useful plan is the ability to estimate reliably. In this session we will discuss how to do this. We will look at various approaches to estimating including unit-less points and ideal time. The class will present four specific techniques for deriving reliable estimates, including how to use the popular Planning Poker® technique and other techniques that dramatically improve a project's chances of on-time completion.
Presentation through Agile University for two day workshop on Agile Scrum conducted in 2010. The objective of the training is to allow attendees to gain knowledge of the Scrum methodology along with the tools for enterprise adoption and change management.
The document provides an overview of Scrum, an Agile framework for project management. It describes Scrum's core roles, events, artifacts, and values. The Product Owner prioritizes goals, the Scrum Master facilitates the process and removes impediments, and the cross-functional Team is self-organizing. Sprints involve planning, daily stand-ups, a taskboard, a sprint review, and a retrospective. Benefits are listed for customers, leadership, and team members, emphasizing feedback, accountability, and sustainable pace. Learning occurs through experience and communities.
- Understand the principles behind the agile approach to software development
- Differentiate between the testing role in agile projects compared with the role of testers in non-agile projects
- Positively contribute as an agile team member focused on testing
- Appreciate the challenges and difficulties associated with the non-testing activities performed in an agile team
- Demonstrate a range of soft skills required by agile team members
The document provides an overview of Scrum, an Agile framework for project management. It describes Scrum's core roles, events, artifacts, and values. The Product Owner prioritizes features, the Scrum Master facilitates the process, and self-organizing Teams work in sprints to deliver working software. Sprints involve planning, daily stand-ups, taskboards to track work, a sprint review to demonstrate work to stakeholders, and a retrospective to improve the process. Customers benefit from early feedback and faster delivery of working products, while teams enjoy sustainable pacing and satisfaction from delivering quality work.
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
Software Development Process Models (SCRUM Methodology)Muhammad Ahmed
This document provides an overview of software process models and Scrum methodology. It defines a software process model as a description of the sequence of activities carried out in a software engineering project. The key activities include specification, design & implementation, validation, and evolution. Scrum is introduced as an agile software development framework. It utilizes short development cycles called sprints, daily stand-up meetings, product backlogs to track requirements, and emphasizes self-organizing teams and adaptive planning. The benefits of Scrum are discussed as improved productivity, quality, and ability to manage changing requirements.
Introduction to Agile and Lean Software DevelopmentThanh Nguyen
The document provides an introduction to agile and lean software development. It discusses traditional vs agile development, defines agile as iterative and incremental using a plan-do-check-act approach with empowered cross-functional teams relying on automation. It covers the agile manifesto, principles and core practices including short iterations, deming's PDCA model, and the agile software development lifecycle. Lean concepts are introduced such as eliminating waste, amplifying learning, deciding late and delivering fast to empower teams and build integrity.
Rich Mironov's keynote for one-day agile workshop. Intro to agile development and agile organizations, tools, impact on whole organization, product management and product planning. Co-sponsored by AccuRev, Coverity, Electric Cloud, Enthiosys, Rally and Agile Journal.
This document provides an overview of different software development processes including the waterfall model, iterative model, Rational Unified Process (RUP), and Agile Development Process (ADP). It describes the key aspects of each process including phases, roles, artifacts, and ceremonies. Specifically, it provides detailed explanations of Scrum, an agile methodology, including Scrum roles like Product Owner and Scrum Master, ceremonies like the Daily Scrum, and artifacts like the Product Backlog and Sprint Backlog. The document concludes with references for further information.
This document provides an overview of Scrum, which is an Agile framework that emphasizes incremental deliveries, quality of product, and continuous improvement. It discusses Scrum roles like Product Owner, ScrumMaster, and Team. The Scrum process involves sprint planning, daily standups, taskboards, sprint reviews, and retrospectives. Benefits are outlined for customers, leadership, and team members. Experiential training and certifications are recommended ways to learn Scrum.
- helps the project manager and technical coordinator in administrative tasks.
- provides support to the team.
Roles
MoSCoW Prioritization
Must Have:
- Critical functionality that must be delivered for the system to be useful.
- Without these features, the system will not meet its basic objectives.
Should Have:
- Important features that should be included if possible after all Must Haves are
complete.
- If not delivered, the system will still be useful but will not meet all objectives.
Could Have:
- Nice to have features that could be included if time and budget permits after
Must Haves and Should Haves are complete.
- Not delivering these features will not significantly
Tue
Wed
Thu
Fri
The document discusses agile software development methodologies and Scrum in particular. It defines agile as iterative and incremental development that promotes adaptive planning, evolutionary development and delivery. Scrum is introduced as an agile process that focuses on delivering the highest business value in the shortest time through short iterative sprints with working software delivered at the end of each sprint. Key Scrum roles, ceremonies, and artifacts like product backlog, sprint backlog, and burn down charts are described.
“Selecting and implementing a new asset finance system? In the second of three articles, we go back to basics to take a look at what you need to consider at the start of your project to give yourself the best chance of success.”
This has necessarily been a brief look at Project Initiation. We welcome comments and would be happy to help you get your project off to a good start.
The Agile Process - Taming Your Process To Work For YouNowell Strite
The document discusses the Agile process and how it aims to address problems with traditional waterfall approaches. It summarizes the key aspects of Agile including:
- Focusing on iterative delivery of working software over comprehensive documentation.
- Emphasizing collaboration and responsiveness to change over strict contracts and plans.
- Using sprints, daily stand-ups, and retrospectives to keep projects on track and continuously improve.
It then provides more details on how Scrum, one flavor of Agile, structures teams, roles, and the sprint life cycle to help deliver working software in a transparent and adaptive manner.
The document provides an overview of agile software development methods. It discusses the history and principles of agile development, including the Agile Manifesto. Specific agile methods like Scrum, XP, RAD, TDD, Crystal and Kanban are covered. For Scrum, it describes the roles of Product Owner, Scrum Master and Development Team. It also explains Scrum events like Sprint Planning, Daily Scrums, Sprint Review and Retrospective. The document aims to give the reader a brief introduction to common agile concepts and practices.
The document provides an overview of agile software development. It discusses the goals of agile, which include gaining an understanding of agile principles and practices. The agenda covers topics like the agile manifesto, roles like product owners and scrum masters, planning practices like backlogs and sprints, reporting, and problems that can occur with agile. Resources for learning more about agile are also provided.
Asset finance system project initiation 101. “Selecting and implementing a new asset finance system? In the second of three articles, we go back to basics to take a look at what you need to consider at the start of your project to give yourself the best chance of success.” This has necessarily been a brief look at Project Initiation. We welcome comments and would be happy to help you get your project off to a good start.
Similar to Online class intro to agile & scrum - final (20)
Scrum is an agile framework that emphasizes incremental deliveries, quality of product, continuous improvement, and discovering people's potential. It uses empiricism, self-organization, prioritization, rhythm, and collaboration. In Scrum, cross-functional teams work in sprints to deliver working software or products frequently using practices like sprint planning, daily standups, taskboards, sprint reviews, and retrospectives. Benefits include faster time to market, engaged teams, and better ability to adapt to change.
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
The document provides an overview of Scrum, an Agile framework. It discusses the Scrum values, roles, practices, and artifacts. The Product Owner prioritizes goals and maintains the product backlog. The Scrum Master facilitates the process and removes impediments. The cross-functional team is self-organizing. Key practices include sprint planning, daily stand-ups, sprint reviews, and retrospectives. Customers benefit from early feedback and faster delivery. Leaders gain better engagement and accountability. Team members enjoy a sustainable pace and satisfaction from delivering quality products. Learning Scrum is best done by applying practices and experiencing the process firsthand.
Scrum is an agile framework that emphasizes incremental deliveries, quality of product, continuous improvement, and discovering people's potential. It uses empiricism, self-organization, prioritization, rhythm, and collaboration. Key roles include the Product Owner who manages the product vision and backlog, the ScrumMaster who facilitates the process and removes impediments, and the cross-functional self-organizing Team. The sprint includes planning, daily standups, taskboards, reviews, and retrospectives to inspect and adapt the product and process. Benefits include faster time to market, engaged teams, and clear priorities.
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
Answers the queries
What do Certified ScrumMaster Trainings involve, who is the certifying authority and how does the certification process work ?Why should you consider getting Certified at all? Does it add value to your career ?How do you take the decision on whether or not to go for certification ?
In other words, is it worth it?
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
This document provides an overview and introduction to Scrum. It begins with an agenda and then covers the overview of Agile and Scrum principles. It describes the core roles in Scrum including the Product Owner, ScrumMaster, and Team. It explains the Scrum events of Sprint Planning, Daily Standup, Sprint Review, and Retrospective. Finally, it discusses the benefits of Scrum for customers, leadership, and team members.
This document provides an overview and introduction to Scrum, an agile framework for managing projects. It discusses the core values and principles of agile and Scrum, including self-organization, empiricism, transparency, commitment, courage, focus, and respect. The key roles of product owner, Scrum master, and development team are explained. An overview of the Scrum process is given, including sprints, planning, daily stand-ups, sprint reviews, and retrospectives. Benefits for customers, leadership, and team members are highlighted. Learning Scrum through experience and communities is encouraged.
Scrum is an agile framework that emphasizes incremental deliveries, quality, and continuous improvement. It uses short development cycles called sprints, daily stand-up meetings, and artifacts like product backlogs and taskboards. Scrum benefits customers through early feedback, faster time to market, and return on investment. It benefits leadership by providing transparency into progress. And it benefits team members by promoting a sustainable pace and the satisfaction of delivering quality products.
The document provides an overview of Scrum, an agile framework. It discusses the Scrum roles of Product Owner, Scrum Master, and Team. It describes Scrum artifacts like the Product Backlog, Sprint Backlog and how daily stand-ups, Sprint Planning, Reviews and Retrospectives work. Benefits are provided for customers, leadership and team members from adopting Scrum.
Main bazar chart Main bazar Jodi Chart Main bazar panel chart Main bazar Matka Main bazar Open Main bazar Result Main bazar Night chart Main bazar night Chart Main bazar Panel Chart 2023 Main bazar matka today Main bazar guessing
#mainbazartoday
#mainbazartrick
#mainbazar
#mainbazarmatka
#mainbazarchart
#satta #kalyantoday
#matka #taramatka #matkaboss
#matka420 #indiaMatka
#sattamattamatka143 #indianMatka
#kalyanchart #kalyanmatka
#kalyanjodichart
#sattabatta #matkaguessing
#indianmatka #matkafixjodi
Satta Matka Satta Matta Matka 143 Kalyan Chart Kalyan Matka Kalyan Satta Matka Fix Jodi Chart Kalyan Panel Chart Dp Boss Matka Guessing 143 24 Satta Batta Matka Boss Otg Kalyan night Chart Milan Night Panel Chart Satta Matka Result India Matka Boss Otg DpBoss Matka Satta Matka Indian Matka Indian Satta Matta Matka 420 Matka Guessing Tara Matka Boss Otg Kalyan Chart Fix Fix Fix Fix Fix Satta Namber Kalyan Jodi Chart Kalyan Satta Kalyan Matka Jodi Fix India Matka India Satta Satta Matta Matka 143 Satta Result Matka Result Satta 143 Satta Batta Kalyan Matka Fix Fix Fix Number
#KALYANTODAY
#KALYANSATTA
#SATTAMATKA
#KalyanJodiChart #KalyanChart #KalyanPanelChart
#mainbazartoday
#mainbazartrick
#mainbazartoday
#mainbazar
KALYAN MATKA | MATKA RESULT | KALYAN MATKA TIPS | SATTA MATKA | MATKA.COM | MATKA PANA JODI TODAY | BATTA SATKA | MATKA PATTI JODI NUMBER | MATKA RESULTS | MATKA CHART | MATKA JODI | SATTA COM | FULL RATE GAME | MATKA GAME | MATKA WAPKA | ALL MATKA RESULT LIVE ONLINE | MATKA RESULT | KALYAN MATKA RESULT | DPBOSS MATKA 143 | MAIN MATKA
Satta Matka Dpboss Kalyan Matka Results Kalyan Chart KALYAN MATKA | MATKA RESULT | KALYAN MATKA TIPS | SATTA MATKA | MATKA.COM | MATKA PANA JODI TODAY | BATTA SATKA | MATKA PATTI JODI NUMBER | MATKA RESULTS | MATKA CHART | MATKA JODI | SATTA COM | FULL RATE GAME | MATKA GAME | MATKA WAPKA | ALL MATKA RESULT LIVE ONLINE | MATKA RESULT | KALYAN MATKA RESULT | DPBOSS MATKA 143 | MAIN MATKA
KALYAN MATKA | MATKA RESULT | KALYAN MATKA TIPS | SATTA MATKA | MATKA.COM | MATKA PANA JODI TODAY | BATTA SATKA | MATKA PATTI JODI NUMBER | MATKA RESULTS | MATKA CHART | MATKA JODI | SATTA COM | FULL RATE GAME | MATKA GAME | MATKA WAPKA | ALL MATKA RESULT LIVE ONLINE | MATKA RESULT | KALYAN MATKA RESULT | DPBOSS MATKA 143 | MAIN MATKA
Satta matka game,matka result,Fastest matka satka batta,matka 420,Matka boss, Kalyan penal Chart,Tara matka, rajdhani night chart, golden dubai matka,sattamatka madhur satta,sattaking143 number weekly jodi,matka guessing final ank open close, Kalyan night chart Indi
an satta King Satta, Kalyan wapka mobi site100 tricks, fix fix fix satta nambar prabhat satta, Kalyan panel chart 2020 2010, SattaMatka, Main ratan panel chart, Mumbai panel chart, Milan panel chart, Kalyan night panel chart, Milan night panel chart, time bazar khiladi420, Sona Matka 111 420, Boss 440, Matka india net, weekly indian Satta fix ank otg, matka one, Simple Matka
Satta Matka Dpboss Kalyan Matka Results Kalyan Chart KALYAN MATKA | MATKA RESULT | KALYAN MATKA TIPS | SATTA MATKA | MATKA.COM | MATKA PANA JODI TODAY | BATTA SATKA | MATKA PATTI JODI NUMBER | MATKA RESULTS | MATKA CHART | MATKA JODI | SATTA COM | FULL RATE GAME | MATKA GAME | MATKA WAPKA | ALL MATKA RESULT LIVE ONLINE | MATKA RESULT | KALYAN MATKA RESULT | DPBOSS MATKA 143 | MAIN MATKA
KALYAN MATKA | MATKA RESULT | KALYAN MATKA TIPS | SATTA MATKA | MATKA.COM | MATKA PANA JODI TODAY | BATTA SATKA | MATKA PATTI JODI NUMBER | MATKA RESULTS | MATKA CHART | MATKA JODI | SATTA COM | FULL RATE GAME | MATKA GAME | MATKA WAPKA | ALL MATKA RESULT LIVE ONLINE | MATKA RESULT | KALYAN MATKA RESULT | DPBOSS MATKA 143 | MAIN MATKA
Satta Matka Dpboss Kalyan Matka Results Kalyan Chart KALYAN MATKA | MATKA RESULT | KALYAN MATKA TIPS | SATTA MATKA | MATKA.COM | MATKA PANA JODI TODAY | BATTA SATKA | MATKA PATTI JODI NUMBER | MATKA RESULTS | MATKA CHART | MATKA JODI | SATTA COM | FULL RATE GAME | MATKA GAME | MATKA WAPKA | ALL MATKA RESULT LIVE ONLINE | MATKA RESULT | KALYAN MATKA RESULT | DPBOSS MATKA 143 | MAIN MATKA
➒➌➎➏➑➐➋➑➐➐ Satta Matka Dpboss Matka Guessing Indian MatkaKALYAN MATKA | MATKA RESULT | KALYAN MATKA TIPS | SATTA MATKA | MATKA.COM | MATKA PANA JODI TODAY | BATTA SATKA | MATKA PATTI JODI NUMBER | MATKA RESULTS | MATKA CHART | MATKA JODI | SATTA COM | FULL RATE GAME | MATKA GAME | MATKA WAPKA | ALL MATKA RESULT LIVE ONLINE | MATKA RESULT | KALYAN MATKA RESULT | DPBOSS MATKA 143 | MAIN MATKA
KALYAN MATKA | MATKA RESULT | KALYAN MATKA TIPS | SATTA MATKA | MATKA.COM | MATKA PANA JODI TODAY | BATTA SATKA | MATKA PATTI JODI NUMBER | MATKA RESULTS | MATKA CHART | MATKA JODI | SATTA COM | FULL RATE GAME | MATKA GAME | MATKA WAPKA | ALL MATKA RESULT LIVE ONLINE | MATKA RESULT | KALYAN MATKA RESULT | DPBOSS MATKA 143 | MAIN MATKA
KALYAN MATKA | MATKA RESULT | KALYAN MATKA TIPS | SATTA MATKA | MATKA.COM | MATKA PANA JODI TODAY | BATTA SATKA | MATKA PATTI JODI NUMBER | MATKA RESULTS | MATKA CHART | MATKA JODI | SATTA COM | FULL RATE GAME | MATKA GAME | MATKA WAPKA | ALL MATKA RESULT LIVE ONLINE | MATKA RESULT | KALYAN MATKA RESULT | DPBOSS MATKA 143 | MAIN MATKA
KALYAN MATKA | MATKA RESULT | KALYAN MATKA TIPS | SATTA MATKA | MATKA.COM | MATKA PANA JODI TODAY | BATTA SATKA | MATKA PATTI JODI NUMBER | MATKA RESULTS | MATKA CHART | MATKA JODI | SATTA COM | FULL RATE GAME | MATKA GAME | MATKA WAPKA | ALL MATKA RESULT LIVE ONLINE | MATKA RESULT | KALYAN MATKA RESULT | DPBOSS MATKA 143 | MAIN MATKA
➒➌➎➏➑➐➋➑➐➐ Satta Matka Dpboss Matka Guessing Indian Matka
KALYAN MATKA | MATKA RESULT | KALYAN MATKA TIPS | SATTA MATKA | MATKA.COM | MATKA PANA JODI TODAY | BATTA SATKA | MATKA PATTI JODI NUMBER | MATKA RESULTS | MATKA CHART | MATKA JODI | SATTA COM | FULL RATE GAME | MATKA GAME | MATKA WAPKA | ALL MATKA RESULT LIVE ONLINE | MATKA RESULT | KALYAN MATKA RESULT | DPBOSS MATKA 143 | MAIN MATKA Satta matka, Kalyan matka,matka guessing,fix matka,satta market,matka market,matka bazar,satta bazar,matka,satta matka result,matka game,matkaresult,Fastest matka satka batta,matka 420,Matka boss, Kalyan penal Chart,Tara matka, rajdhani night chart, golden dubai matka,sattamatka madhur satta,sattaking143 number weekly jodi,matka guessing final ank open close, Kalyan night chart Indian satta King Satta, Kalyan wapka mobi site100 tricks, fix fix fix satta nambar prabhat satta, Kalyan panel chart 2020 2010, SattaMatka, Main ratan panel chart, Mumbai panel chart, Milan panel chart, Kalyan night panel chart, Milan night panel chart, time bazar khiladi420, Sona Matka 111 420, Boss 440, Matka india net, weekly indian Satta fix ank otg, matka one, Simple Matka Guessing Param Matka guessing trick 143 surya Alex, satta, dpboss, SattaMatka, Boss Matka, Matka Boss, Satta Boss, Matka Satta,Sata Mataka, Satta Mataka, Satta Matka net, Satta Matka.com, Satta Matka Chart, Kalyan Matka Result, Today Matka Jodi, Kalyan Main Matka tips, Kalyan Matka Guru, Aaj ka satta Kalyan Jodi, today satta number, Satta Matta Matka, sata matka, satta result, rajshree matka result, satta Kalyan, satta matka com, satta matka mobi, Matka boss, sattamatka143, sattabatta, indianmatka, result matka, sattaka matka com, satta matka.net, Kalyan chart, Kalyan result, Kalyan penal Chart, Kalyan satta, satta matka Kalyan, satta matka com, satta matka net, satta batta, fix fix fix satta number, Satta Matka 143, ka matka, worli matka, matka bajar, Satta Matta Matka 143, satta chart, Satta Matka guessing, Satta, matka 420, Satta Matta Matka and Matka result, Satta Matka, all Matka, Setka Matka, Matta Matká, Satta m, india Matka, Matká Satta, Matka Boss otg, Indian Matka guessing, final ank,final ank open, final ank jodi, final ank guessing, Satta matka 420, matka satta 420,
#Satta Matka #Satta Matka Guessing #Kalyan Matka Guessing #Matka Guessing Forum #Matka Guessing 143 #Simple Matka Guessing #Matka Trick #Dpboss Guessing #Satta Matka 143 Guessing #Satta Matka God #Satta King Guess #Free Matka Guessing #Kalyan Matka Trick #Satta Matka Gods #Satta King Guessing #Satta Matka #Matka Guessing #Satta #Matka #Satta Matta Matka #Matka Result #Satka Matka #all Matka #Setka Matka #Matta Matkà #Kalyan Matka #Indian Matka #Sattamatka #Matka Satta #Satta.Matka #Kalyan Chart #Kalyan penal Chart #Matka Guessing #Matka Boss otg #Matka 420 #matka Indian Matka,Matka Boss Otg, Free Matka Boss, Matka 420 #Matka 786 #Kalyan Guessing #Satta Guessing #dpboss.social #dpboss.guru #dpboss.expert#dpbosss.com#SATTA_MATKA_KALYAN_H
Satta Matka Kalyan Satta Matka guessing Kalyan Open Kalyan Jodi Chart #kalyantoday #kalyantrick #kalyanopen #kalyanguessing #kalyanresult
kalyan chart kalyan matka satta matka kalyan open satta kalyan close kalyan today satta matka kalyan
kalyan matka trick sattamatka kalyan result sattamattamatka kalyan guessing today kalyan trick satta matka kalyan result कल्याण मटका satta matka trick result kalyan matka kalyan satta matka result today kalyan fix jodi sattamatkakalyanchart kalyan bazar kalyan fix jodi kalyan aaj ki jodi kalyan aaj ka open kalyan fix today
KALYAN MATKA | MATKA RESULT | KALYAN MATKA TIPS | SATTA MATKA | MATKA.COM | MATKA PANA JODI TODAY | BATTA SATKA | MATKA PATTI JODI NUMBER | MATKA RESULTS | MATKA CHART | MATKA JODI | SATTA COM | FULL RATE GAME | MATKA GAME | MATKA WAPKA | ALL MATKA RESULT LIVE ONLINE | MATKA RESULT | KALYAN MATKA RESULT | DPBOSS MATKA 143 | MAIN MATKA
SattaMatka, Boss Matka, Matka Boss, Satta Boss, Matka Satta,Sata Mataka, Satta Mataka, Satta Matka net, Satta Matka.com, Satta Matka Chart, Kalyan Matka Result, Today Matka Jodi, Kalyan Main Matka tips, Kalyan Matka Guru, Aaj ka satta Kalyan Jodi, today satta number, Satta Matta Matka, sata matka, satta result, rajshree matka result, satta Kalyan, satta matka com, satta matka mobi, Matka boss, sattamatka143, sattabatta, indianmatka, result matka, sattaka matka com, satta matka.net, Kalyan chart, Kalyan result, Kalyan penal Chart, Kalyan satta, satta matka Kalyan, satta matka com, satta matka net, satta batta, fix fix fix satta number, Satta Matka 143, ka matka, worli matka, matka bajar, Satta Matta Matka 143, satta chart, Satta Matka guessing, Satta, matka 420, Satta Matta Matka and Matka result, Satta Matka, all Matka, Setka Matka, Matta Matká, Satta m, india Matka, Matká Satta, Matka Boss otg, Indian Matka guessing, final ank,final ank open, final ank jodi, final ank guessing, Satta matka 420, matka satta 420,
#Satta Matka #Satta Matka Guessing #Kalyan Matka Guessing #Matka Guessing Forum #Matka Guessing 143 #Simple Matka Guessing #Matka Trick #Dpboss Guessing #Satta Matka 143 Guessing #Satta Matka God #Satta King Guess #Free Matka Guessing #Kalyan Matka Trick #Satta Matka Gods #Satta King Guessing #Satta Matka #Matka Guessing #Satta #Matka #Satta Matta Matka #Matka Result #Satka Matka #all Matka #Setka Matka #Matta Matkà #Kalyan Matka #Indian Matka #Sattamatka #Matka Satta #Satta.Matka #Kalyan Chart #Kalyan penal Chart #Matka Guessing #Matka Boss otg #Matka 420 #matka Indian Matka,Matka Boss Otg, Free Matka Boss, Matka 420 #Matka 786 #Kalyan Guessing #Satta Guessing #dpboss.social #dpboss.guru #dpboss.expert#dpbosss.com#SATTA_MATKA_KALYAN_HEAD_OFFICE #sattamatkaresult.in#dpboss #sattamatkaresult #Indiana #Setka #KALYAN#Mattapan #SATTA #satka #allnatural #SattaMatka #indianwedding #FreeGame #matta#kalyanmatka #matkaboss #Matka420 #indianMatka #KalyanChart #matkaotg #sattatrick #MAINBAZAR #kalyanjodichart #indiaMatka
KALYAN MATKA | MATKA RESULT | KALYAN MATKA TIPS | SATTA MATKA | MATKA.COM | MATKA PANA JODI TODAY | BATTA SATKA | MATKA PATTI JODI NUMBER | MATKA RESULTS | MATKA CHART | MATKA JODI | SATTA COM | FULL RATE GAME | MATKA GAME | MATKA WAPKA | ALL MATKA RESULT LIVE ONLINE | MATKA RESULT | KALYAN MATKA RESULT | DPBOSS MATKA 143 | MAIN MATKA
KALYAN MATKA | MATKA RESULT | KALYAN MATKA TIPS | SATTA MATKA | MATKA.COM | MATKA PANA JODI TODAY | BATTA SATKA | MATKA PATTI JODI NUMBER | MATKA RESULTS | MATKA CHART | MATKA JODI | SATTA COM | FULL RATE GAME | MATKA GAME | MATKA WAPKA | ALL MATKA RESULT LIVE ONLINE | MATKA RESULT | KALYAN MATKA RESULT | DPBOSS MATKA 143 | MAIN MATKA
2. Agenda2Intro to Agile & ScrumScrum FrameworkScrum RolesPlanning & EstimationTeam EngagementQ&A - Class feedbackCopyright Conscires 20112
3. Agile Manifesto3Individuals and interactions over processes and tools Working software/product over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Copyright Conscires 20113
5. Agile 12 Principles5Highest priority is to satisfy the customerthrough early and continuous deliveryof valuable softwareWelcome changing requirementsDeliver working software (Product) frequentlyBusiness people and developers must work together daily throughout the projectBuild projects around motivated individualsMost efficient and effective method of conveying information is face-to-face conversationCopyright Conscires 20115
6. Agile 12 Principles6Working software (product) is the primary measure of progressAgile processes promote sustainable development (maintain a constant pace indefinitely)Continuous attention to technical excellence and good design enhances agilitySimplicity (art of maximizing amount of work not done) is essentialBest architectures, requirements, and designs emerge from self-organizing teamsAt regular intervals, team reflects on how to become more effective, then tunes and adjustshttp://agilemanifesto.org/principles.htmlCopyright Conscires 20116
7. Scrum Foundation7Empiricism Detailed up-front planning and defined processes are replaced by just-in-time Inspect and Adapt cyclesSelf-OrganizationSmall teams manage their own workload and organize themselves around clear goals and constraintsPrioritizationDo the next right thingRhythmAllows teams to avoid daily noise and focus on deliveryCollaborationLeaders and customers work with the Team, rather than directing themCopyright Conscires 20117
8. Scrum Values8TransparencyEverything about a project is visible to everyoneCommitmentBe willing to commit to a goalCourageHave the courage to commit, to act, to be open and to expect respectFocusFocus all of your efforts and skills on doing the work that you have committed to doingRespectRespect and trust the different people who comprise a teamCopyright Conscires 20118
11. Scrum Roles11Product OwnerMaximize the value of the work done by prioritizing the features by market valueScrum MasterManages the Scrum frameworkTeamSelf-organizing empowered individuals motivated by business goalsOther StakeholdersAnyone who needs something from the team or the team something fromCopyright Conscires 201111
12. Scrum Roles Details – Product Owner12Thought Leader and VisionaryDrives the Product Vision (for example, with Story Mapping)Prioritizes the User Stories Maintains the Product Backlog with the teamAccepts the Working Product (on behalf of the customer)Copyright Conscires 201112
13. Scrum Roles Details – Scrum Master13Servant LeaderFacilitates the ProcessSupports the TeamRemoves Organizational ImpedimentsSocializes Scrum to ManagementEnable close collaboration across all roles and functionsCopyright Conscires 201113
16. Management Roles (Servant Leadership)16Is a servant first and ensures other people – i.e. followers or stakeholders – highest priority needs are being served Empowers others and supports an environment of trust Has empathy and sensitivity to the needs and interest of all stakeholders Is open to the voice of others by supporting discussions that includes those without a voiceAccept risks; takes the risk of failure along with the chance of success, while trusting others My cup is always full – my focus is now; I’ve learned from yesterday and I’m planning for tomorrowCopyright Conscires 201116
18. Pre-Scrum Planning18Pre-Scrum is where projects are approved, budgets and resources assigned Project Portfolio’s are expensiveThey are riskyDo we have the right people with the right experience and skills?Can we afford the project?What are the objectives of the project? Clear goals.Lack of commitmentCan we verify the promise was met?The business want value and a return on investmentCopyright Conscires 201118
26. Product Vision & Role Engagement21A goal to aspire toCan be summarized in a short statement of intentCommunicate it to the teamCommon format:For: (Our Target Customer)Who: (Statement of need)The: (Product/Product name) is a (Product/Product category)That: (Product/Product key benefit, compelling reason to buy and/or use)Unlike: (Primary competitive alternative)Our Product: (Final statement of primary differentiation)Copyright Conscires 201121
27. Product Backlog22A living list of requirements captured in the form of User StoriesRepresents the WHAT of the systemPrioritization with respect to business value is essential!Each story has estimated Story Points, which represent relative size, and is determined by those actually doing the workHigher priority items are decomposed and lower priority items are left as larger stories (epics)Copyright Conscires 201122
28. Relative Estimation23Humans are better at relative estimates than absolute estimatesMany heads are better than oneEstimates are made by those who perform the workEstimate size/complexity – Derive durationThe goal is to get useful estimates with minimal effortEstimates are not commitmentsPlanning Poker is the common method for estimationCopyright Conscires 201123
30. Relative Estimation25Story Points:Commonly used in Agile estimationNo real-world dimensionsCompare one story to anotherBased on effort, complexity, riskPrecision is not criticalCopyright Conscires 201125
31. Scrum Release - Velocity26Total number of story points completed by a team in a SprintCan be used by the team as a reference during Sprint PlanningUsed by Product Owner to plan out the releasesCopyright Conscires 201126
32. Scrum Release Planning27Product Owner, in conjunction with the team, formulates Release Plans by applying the team Velocity to the Product BacklogRelease Plans are revisited after every SprintTwo ways to approachFix scope and determine how many sprints are neededFix time and determine how much scope can be completedCopyright Conscires 201127
33. User Stories28Product requirements formulated as one or more sentences in the everyday or business language of the userAs a <user>, I would like <function> so that I get <value>Each User Story has an associated Acceptance Criteria that is used to determine if the Story is completedCopyright Conscires 201128
34. Sprint Backlog29List of stories, broken down into tasks, that is committed for any particular SprintOwned and managed by the TeamAny team member can add, delete or change the sprint backlog with additional tasksCopyright Conscires 201129
35. User Stories30IndependentNot overlap in concept and be able to schedule and implement them in any orderNegotiableNot an explicit contract for features; rather, details will be co-created by Product Owner and TeamValuableAdd business valueEstimatedJust enough to help the Product Owner rank and schedule the story's implementationSized AppropriatelyNeed to be small, such as a few person-daysTestableA characteristic of good requirementsCopyright Conscires 201130
36. Task Board31Active visual indicator of flow of workShould be visible to team members at all timesShould be kept currentEncourages self-organization, and collaborationCopyright Conscires 201131
37. DOD - (Definition of Done)32Team creates its own definition of Done in the interest of creating quality softwareDefinition can evolve over sprintsExample checklist (not exhaustive):Unit tests pass (ideally automated)Customer Acceptance tests passUser docs writtenUI design approved by POIntegrated into existing systemRegression test/s pass (ideally automated)Deployed on staging serverPerformance tests passCopyright Conscires 201132
39. Sprint Burn-down34Shows daily progress in the SprintX-axis is the number of days in the SprintY-axis is the number of remaining storiesCopyright Conscires 201134
40. Release Burn-down35Shows progress across SprintsX-axis is the number of SprintsY-axis is the total number of storiesCopyright Conscires 201135
41. Daily Standup Meetings36Meetings held in same location, same time, every dayTime-boxed at 15 minutesEncourages self-organization, rhythm, and collaborationNot a status meetingEach Team member speaks to:What did I accomplish in the last 24 hoursWhat do I plan to accomplish in the next 24 hoursAny impediments getting in the way of my workCopyright Conscires 201136
42. Sprint Planning37Sprint Planning meeting held at beginning of each SprintTime and Resources are fixed in any given Sprint Goal is to have prioritized Sprint Backlog, broken down into tasks, that the Team can commit toDuring planning, Team commits to scope that can be completed in the Sprint, taking into account the definition of DoneStory points may be refinedCopyright Conscires 201137
43. Sprint Review38Occurs at the end of each SprintInspect and Adapt the product (Empiricism)The team meets with the Product Owner (and Stakeholders) to demonstrate the working software from the SprintThis is a hands-on software demo (not a PowerPoint) that usually requires some prep beforehandCopyright Conscires 201138
44. Retrospectives39Occurs at the end of each SprintInspect and Adapt the process (Empiricism)Team and ScrumMaster meet to reflect on what went well and what can be improvedTone of the meeting is that everyone did their best and now look to how can we improveRetrospectives must conclude with team commitments to actionCopyright Conscires 201139
45. Scrum Myths40Scrum Myths:No quality/no testingPeople burnout because of short and frequent delivery cycles (sprints)No culture change is neededWill make a better teamScrum is the only Agile methodSolution to allCopyright Conscires 201140
47. Scrum Myths42Scrum Myths:A silver bulletManagement believes it will solve all problemsEasy to implementCowboy codingNo documentationCopyright Conscires 201142
56. Take Away44Scrum is a lightweight framework with a simple set of rules, built on foundations and values
57. Scrum enables teams to discover their true potential and deliver quality software that adds business valueCopyright Conscires 201144
58. Appendix - Roles45Product OwnerThought Leader and Visionary, who drives the Product Vision, maintains the Product Backlog, prioritizes the User Stories, and accepts the Working Software (on behalf of the customer)ScrumMasterServant Leader, who facilitates the process, supports the Team, removes organizational impediments, and socializes Scrum to ManagementTeamCross-Functional group of 5-8 Members that is self-organizing and focused on meeting CommitmentsCopyright Conscires 201145
59. Appendix – Artifacts46Product BacklogA living list of requirements captured in the form of User Stories, prioritized according to business valueSprint BacklogList of stories, broken down into tasks, that is committed for any particular Sprint; owned and managed by the TeamTaskboardActive visual indicator of flow of workSprint Burndown ChartShows daily progress in the SprintRelease Burndown ChartShows progress across SprintsCopyright Conscires 201146
60. Appendix - Ceremonies47Sprint PlanningHeld at beginning of each Sprint, with the goal to have prioritized Sprint Backlog, broken down into tasks, that the Team can commit toDaily StandupMeetings held in same location, same time, every day, with the goal of ensuring that team members are in synch (not a status meeting)Sprint ReviewOccurs at the end of each Sprint, with the goal of inspecting and adapting the ProductRetrospectiveOccurs at the end of each Sprint, with the goal of inspecting and adapting the processCopyright Conscires 201147