This document provides an overview of managing scope, time, cost, and team in Agile frameworks like Scrum. It discusses key Scrum concepts like artifacts, roles, ceremonies and how they relate to traditional project management. Scope, time and team are fixed within sprints in Scrum, unlike the waterfall model where scope is fixed upfront. Cost is estimated and budgets are determined, with value-driven development. Self-organizing cross-functional teams work in short sprints to deliver working software frequently using practices that enhance responding to change over rigid plans.
This is one of the very best presentations about scrum that I know of and thought it worthwhile to have it up for people to be able to check it out. It's great that the authors went for a Creative Commons license.
The document discusses Agile Scrum, including:
- The Agile Manifesto principles of prioritizing individuals, interactions, working software, and responding to change over processes, tools, documentation, and following a plan.
- Scrum roles like Product Owner, Scrum Master, and cross-functional team members.
- Scrum ceremonies like sprint planning, daily stand-ups, sprint reviews, and retrospectives.
- User stories, epics, and conditions of satisfaction to define work in the product backlog.
- The goal of each sprint is to produce potentially shippable increments of functionality.
The document provides an overview of the waterfall model and agile methodologies for software development projects. It discusses:
- The linear sequential phases of the waterfall model and when it is suitable.
- Issues with the waterfall model like inability to handle changes and lack of testing throughout.
- Benefits of agile like ability to adapt to changes, early delivery of working software, and improved success rates.
- Key aspects of the Scrum agile framework like sprints, daily stand-ups, and product backlogs.
- Differences in how development costs are treated as capital expenditures or operating expenses between waterfall, agile, and cloud-based models.
The document provides an overview of the Agile Scrum process. It describes traditional waterfall methodologies and how Agile and Scrum differ by being more iterative, collaborative with stakeholders, and able to adapt to changes. The Scrum framework involves three main roles - Product Owner, Scrum Master, and Team. It also describes the four main Scrum ceremonies - Sprint Planning Meeting, Daily Standup, Sprint Review, and Sprint Retrospective - as well as the typical artifacts like Product Backlog and Sprint Backlog.
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
The document provides an overview of Scrum, an agile framework for project management. It discusses the core components of Scrum including roles, artifacts, ceremonies, and values. The key roles are Product Owner, Scrum Master, and self-organizing Team. Projects progress through a series of sprints where work is pulled from the prioritized Product Backlog to the Sprint Backlog and completed work is demonstrated at Sprint Review meetings. Daily stand-up meetings and retrospective meetings aid in transparency and process improvement.
Waterfall vs agile approach scrum framework and best practices in software d...Tayfun Bilsel
The document discusses various topics related to software development approaches, including:
1. The differences between waterfall and agile approaches. Agile focuses on iterative development and responding to change over extensive planning.
2. Common problems with traditional project management like late delivery and budget overruns.
3. An overview of the Scrum framework, including roles, artifacts, ceremonies, and best practices. Scrum uses short iterations called sprints to iteratively deliver working software.
4. Recommendations to customize Scrum by incorporating elements of eXtreme Programming (XP) and lean principles to eliminate waste and continually improve processes.
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018
This is one of the very best presentations about scrum that I know of and thought it worthwhile to have it up for people to be able to check it out. It's great that the authors went for a Creative Commons license.
The document discusses Agile Scrum, including:
- The Agile Manifesto principles of prioritizing individuals, interactions, working software, and responding to change over processes, tools, documentation, and following a plan.
- Scrum roles like Product Owner, Scrum Master, and cross-functional team members.
- Scrum ceremonies like sprint planning, daily stand-ups, sprint reviews, and retrospectives.
- User stories, epics, and conditions of satisfaction to define work in the product backlog.
- The goal of each sprint is to produce potentially shippable increments of functionality.
The document provides an overview of the waterfall model and agile methodologies for software development projects. It discusses:
- The linear sequential phases of the waterfall model and when it is suitable.
- Issues with the waterfall model like inability to handle changes and lack of testing throughout.
- Benefits of agile like ability to adapt to changes, early delivery of working software, and improved success rates.
- Key aspects of the Scrum agile framework like sprints, daily stand-ups, and product backlogs.
- Differences in how development costs are treated as capital expenditures or operating expenses between waterfall, agile, and cloud-based models.
The document provides an overview of the Agile Scrum process. It describes traditional waterfall methodologies and how Agile and Scrum differ by being more iterative, collaborative with stakeholders, and able to adapt to changes. The Scrum framework involves three main roles - Product Owner, Scrum Master, and Team. It also describes the four main Scrum ceremonies - Sprint Planning Meeting, Daily Standup, Sprint Review, and Sprint Retrospective - as well as the typical artifacts like Product Backlog and Sprint Backlog.
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
The document provides an overview of Scrum, an agile framework for project management. It discusses the core components of Scrum including roles, artifacts, ceremonies, and values. The key roles are Product Owner, Scrum Master, and self-organizing Team. Projects progress through a series of sprints where work is pulled from the prioritized Product Backlog to the Sprint Backlog and completed work is demonstrated at Sprint Review meetings. Daily stand-up meetings and retrospective meetings aid in transparency and process improvement.
Waterfall vs agile approach scrum framework and best practices in software d...Tayfun Bilsel
The document discusses various topics related to software development approaches, including:
1. The differences between waterfall and agile approaches. Agile focuses on iterative development and responding to change over extensive planning.
2. Common problems with traditional project management like late delivery and budget overruns.
3. An overview of the Scrum framework, including roles, artifacts, ceremonies, and best practices. Scrum uses short iterations called sprints to iteratively deliver working software.
4. Recommendations to customize Scrum by incorporating elements of eXtreme Programming (XP) and lean principles to eliminate waste and continually improve processes.
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018
This document provides a summary of key concepts from Chapter 4 of the book "Essential Scrum". It describes the Scrum framework, roles, artifacts, and events. The Scrum roles include the Product Owner, Scrum Master, and Development Team. Key artifacts are the Product Backlog and Sprint Backlog. Main events are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The goal is to help teams self-organize to deliver working software in short cycles through transparency, inspection, and adaptation.
The "2017 Scrum by Picture" is something you can call Scrum Guide illustrated. It is based on the newest version of "Scrum Guide".
You will find the theory, scrum values, scrum team, scrum events including sprint, sprint planning, daily scrum, review and retrospective as well as scrum artifacts. All of those is explained in easy to follow, illustrated nicely presentation, which can assist you to catch the idea behind Scrum.
Feel free to share "2017 Scrum by Picture" with your Scrum friends.
The document discusses how adopting Agile practices can help reduce costs and increase project success rates. It provides an overview of the Agile manifesto and techniques like iterative development, improved communication, and leverage existing investments. Adopting Agile can lead to reduced inventory, quick turnaround focusing on required functionality, minimizing costs, and delivering working software sooner to generate savings and quicker time to market. This allows for a focus on ROI and increased project success rates through improved quality, productivity, visibility for customers, and alignment between business and technology needs.
This document provides an introduction to the Scrum framework for agile software development. It describes Scrum as an iterative, incremental framework that uses self-organizing cross-functional teams to deliver complex products. The key aspects of Scrum covered include the roles of product owner, Scrum master and development team, the Scrum events of sprint planning, daily stand-ups, sprint reviews and retrospectives, and the artifacts of product and sprint backlogs and burn-down charts. The document provides an overview of how Scrum is intended to provide transparency, inspection, and adaptation to optimize predictability and control of risk.
Scrum is an agile framework for managing projects that uses short cycles of work called sprints to incrementally deliver working software. There are three main roles in Scrum - the Product Owner prioritizes features in the Product Backlog, the Scrum Master facilitates the process, and the self-organizing Team works to complete the highest priority items each sprint. Key Scrum artifacts include the Product Backlog, Sprint Backlog, and Burn Down Chart. The main Scrum ceremonies are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective meetings.
This document provides an overview of Agile methodology and Scrum framework. It defines key Agile concepts like iterations called sprints and artifacts like product backlog, sprint backlog, and product increment. It describes Scrum roles of product owner, Scrum master, and team. It outlines Scrum activities like sprint planning, daily scrum, sprint review, and retrospective. Finally, it discusses tools like task boards and burn down charts used to provide transparency and track progress.
The document provides an introduction to Agile methodology and Scrum framework. It discusses the limitations of traditional waterfall approaches and how Agile and Scrum address those limitations through iterative development with frequent delivery and ability to adapt to changing requirements. The key aspects of Scrum like sprints, daily stand-ups, sprint planning, review and retrospective are explained to give an overview of how Scrum works in practice.
Introduction to Project Management with ScrumPierre E. NEIS
It's a small presentation to give the basic principles of scrum.
The presentation mode is made interactively with the audience.
The progression of the slides are scaled on progessive learning and fixing process: starting from theory to practice.
It's not enough to start a Scrum Project and do not replace a mature scrum training delivered by a senior Scrum Trainer.
The document discusses the Agile Scrum methodology. It describes the key principles of Scrum which value individuals and interaction, working software, customer collaboration, and responding to change over processes, documentation, contracts, and plans. It then explains the main roles in Scrum including the Product Owner, Scrum Master, and self-organizing cross-functional Team. It outlines the core Scrum events like the Sprint, Daily Stand-up, Sprint Review, and Retrospective.
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
This document provides an overview of Scrum, an agile project management framework. Some key points:
- Scrum uses iterative "Sprints" typically lasting 2-4 weeks to develop software in short cycles. A product backlog is prioritized and tasks are broken down for each Sprint.
- Self-organizing Scrum teams of 5-9 people work to complete the Sprint goals. Daily stand-up meetings provide status updates and help remove impediments.
- At the end of each Sprint, working software is demonstrated and the product owner evaluates progress before prioritizing tasks for the next Sprint.
- Scrum aims to improve productivity, adaptability and creativity compared to
This document provides an introduction to Agile project management frameworks like Scrum and Kanban. It discusses the limitations of traditional waterfall project management and how Agile aims to address these issues through iterative development, collaboration, and flexibility. Key aspects of Scrum like roles, events, artifacts, estimation and user stories are explained. Kanban concepts such as visualizing workflow, limiting work in progress, and managing flow are also covered. The document recommends resources for learning more about Agile, Scrum, Kanban and hybrid approaches.
This document provides an introduction to Agile and Scrum. It discusses the principles of Agile, including the Agile Manifesto. Scrum is presented as an Agile framework consisting of roles, ceremonies, and artifacts. The roles of Product Owner, Scrum Master, and Engineering Team are defined. Ceremonies like Sprint Planning, Daily Scrum, Sprint Review and Retrospective are explained. Artifacts such as Product Backlog, Sprint Backlog and Burn Down Chart are also summarized. User stories, estimation techniques, and definitions of done are covered as part of requirements and planning in Scrum.
The document provides an overview of agile software development and the Scrum framework. It discusses the motivation for agile methods in response to traditional "cowboy coding" and waterfall models. The key aspects of Scrum covered include its core principles, roles of Product Owner, Scrum Master and team members, artifacts like product and sprint backlogs and task boards, ceremonies like the daily scrum, and rules. The takeaways emphasized by the document are that the Scrum foundations provide comprehensive guidance but its application should be practical and simple, with the right combination being most effective.
Scrum is an agile framework for managing product development that emphasizes self-organizing cross-functional teams, sprints, daily stand-ups, and adaptive planning. It consists of roles like the product owner and Scrum master, artifacts like the product backlog and sprint backlog, and ceremonies like sprint planning and reviews. Scrum originated in the 1990s and aims to rapidly deliver working software through short development cycles and continuous improvement.
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.
- Scrum is an agile framework for managing product development, with roles of Product Owner, Scrum Master, and Development Team.
- Key rituals include Sprint Planning, Daily Stand-ups, Sprint Review and Retrospective.
- The Product Owner prioritizes features in the Product Backlog to maximize business value, while the Development Team works in sprints to deliver increments of functionality. The Scrum Master facilitates the process and removes impediments.
This document provides an overview of agile estimation techniques for fixed price projects. It discusses challenges with upfront estimation for fixed price contracts and recommends estimating projects using fixed costs rather than fixed scope. The document outlines a 14-step framework for agile story point estimation, planning and scheduling that includes defining requirements, user stories, estimating story points using matrices, computing initial velocity, and determining schedules and additional efforts. It also discusses change management processes and factors that can impact velocity like team expertise and requirement clarity.
Backlog Grooming - The Importance of Good Grooming HabitsIan Garrison
The document discusses backlog grooming meetings, which are meetings held by the product owner, scrum master, development team, and other stakeholders to prepare stories in the product backlog for upcoming sprints. It provides guidance on when and how frequently to hold grooming meetings, who should attend, and best practices for ensuring stories meet criteria for being ready to be pulled into a sprint, such as breaking down stories, using personas, and focusing on only having meaningful conversations. The goal of effective grooming is to provide transparency and predictability for the team while reducing rework.
This document provides a summary of key concepts from Chapter 4 of the book "Essential Scrum". It describes the Scrum framework, roles, artifacts, and events. The Scrum roles include the Product Owner, Scrum Master, and Development Team. Key artifacts are the Product Backlog and Sprint Backlog. Main events are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The goal is to help teams self-organize to deliver working software in short cycles through transparency, inspection, and adaptation.
The "2017 Scrum by Picture" is something you can call Scrum Guide illustrated. It is based on the newest version of "Scrum Guide".
You will find the theory, scrum values, scrum team, scrum events including sprint, sprint planning, daily scrum, review and retrospective as well as scrum artifacts. All of those is explained in easy to follow, illustrated nicely presentation, which can assist you to catch the idea behind Scrum.
Feel free to share "2017 Scrum by Picture" with your Scrum friends.
The document discusses how adopting Agile practices can help reduce costs and increase project success rates. It provides an overview of the Agile manifesto and techniques like iterative development, improved communication, and leverage existing investments. Adopting Agile can lead to reduced inventory, quick turnaround focusing on required functionality, minimizing costs, and delivering working software sooner to generate savings and quicker time to market. This allows for a focus on ROI and increased project success rates through improved quality, productivity, visibility for customers, and alignment between business and technology needs.
This document provides an introduction to the Scrum framework for agile software development. It describes Scrum as an iterative, incremental framework that uses self-organizing cross-functional teams to deliver complex products. The key aspects of Scrum covered include the roles of product owner, Scrum master and development team, the Scrum events of sprint planning, daily stand-ups, sprint reviews and retrospectives, and the artifacts of product and sprint backlogs and burn-down charts. The document provides an overview of how Scrum is intended to provide transparency, inspection, and adaptation to optimize predictability and control of risk.
Scrum is an agile framework for managing projects that uses short cycles of work called sprints to incrementally deliver working software. There are three main roles in Scrum - the Product Owner prioritizes features in the Product Backlog, the Scrum Master facilitates the process, and the self-organizing Team works to complete the highest priority items each sprint. Key Scrum artifacts include the Product Backlog, Sprint Backlog, and Burn Down Chart. The main Scrum ceremonies are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective meetings.
This document provides an overview of Agile methodology and Scrum framework. It defines key Agile concepts like iterations called sprints and artifacts like product backlog, sprint backlog, and product increment. It describes Scrum roles of product owner, Scrum master, and team. It outlines Scrum activities like sprint planning, daily scrum, sprint review, and retrospective. Finally, it discusses tools like task boards and burn down charts used to provide transparency and track progress.
The document provides an introduction to Agile methodology and Scrum framework. It discusses the limitations of traditional waterfall approaches and how Agile and Scrum address those limitations through iterative development with frequent delivery and ability to adapt to changing requirements. The key aspects of Scrum like sprints, daily stand-ups, sprint planning, review and retrospective are explained to give an overview of how Scrum works in practice.
Introduction to Project Management with ScrumPierre E. NEIS
It's a small presentation to give the basic principles of scrum.
The presentation mode is made interactively with the audience.
The progression of the slides are scaled on progessive learning and fixing process: starting from theory to practice.
It's not enough to start a Scrum Project and do not replace a mature scrum training delivered by a senior Scrum Trainer.
The document discusses the Agile Scrum methodology. It describes the key principles of Scrum which value individuals and interaction, working software, customer collaboration, and responding to change over processes, documentation, contracts, and plans. It then explains the main roles in Scrum including the Product Owner, Scrum Master, and self-organizing cross-functional Team. It outlines the core Scrum events like the Sprint, Daily Stand-up, Sprint Review, and Retrospective.
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
This document provides an overview of Scrum, an agile project management framework. Some key points:
- Scrum uses iterative "Sprints" typically lasting 2-4 weeks to develop software in short cycles. A product backlog is prioritized and tasks are broken down for each Sprint.
- Self-organizing Scrum teams of 5-9 people work to complete the Sprint goals. Daily stand-up meetings provide status updates and help remove impediments.
- At the end of each Sprint, working software is demonstrated and the product owner evaluates progress before prioritizing tasks for the next Sprint.
- Scrum aims to improve productivity, adaptability and creativity compared to
This document provides an introduction to Agile project management frameworks like Scrum and Kanban. It discusses the limitations of traditional waterfall project management and how Agile aims to address these issues through iterative development, collaboration, and flexibility. Key aspects of Scrum like roles, events, artifacts, estimation and user stories are explained. Kanban concepts such as visualizing workflow, limiting work in progress, and managing flow are also covered. The document recommends resources for learning more about Agile, Scrum, Kanban and hybrid approaches.
This document provides an introduction to Agile and Scrum. It discusses the principles of Agile, including the Agile Manifesto. Scrum is presented as an Agile framework consisting of roles, ceremonies, and artifacts. The roles of Product Owner, Scrum Master, and Engineering Team are defined. Ceremonies like Sprint Planning, Daily Scrum, Sprint Review and Retrospective are explained. Artifacts such as Product Backlog, Sprint Backlog and Burn Down Chart are also summarized. User stories, estimation techniques, and definitions of done are covered as part of requirements and planning in Scrum.
The document provides an overview of agile software development and the Scrum framework. It discusses the motivation for agile methods in response to traditional "cowboy coding" and waterfall models. The key aspects of Scrum covered include its core principles, roles of Product Owner, Scrum Master and team members, artifacts like product and sprint backlogs and task boards, ceremonies like the daily scrum, and rules. The takeaways emphasized by the document are that the Scrum foundations provide comprehensive guidance but its application should be practical and simple, with the right combination being most effective.
Scrum is an agile framework for managing product development that emphasizes self-organizing cross-functional teams, sprints, daily stand-ups, and adaptive planning. It consists of roles like the product owner and Scrum master, artifacts like the product backlog and sprint backlog, and ceremonies like sprint planning and reviews. Scrum originated in the 1990s and aims to rapidly deliver working software through short development cycles and continuous improvement.
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.
- Scrum is an agile framework for managing product development, with roles of Product Owner, Scrum Master, and Development Team.
- Key rituals include Sprint Planning, Daily Stand-ups, Sprint Review and Retrospective.
- The Product Owner prioritizes features in the Product Backlog to maximize business value, while the Development Team works in sprints to deliver increments of functionality. The Scrum Master facilitates the process and removes impediments.
This document provides an overview of agile estimation techniques for fixed price projects. It discusses challenges with upfront estimation for fixed price contracts and recommends estimating projects using fixed costs rather than fixed scope. The document outlines a 14-step framework for agile story point estimation, planning and scheduling that includes defining requirements, user stories, estimating story points using matrices, computing initial velocity, and determining schedules and additional efforts. It also discusses change management processes and factors that can impact velocity like team expertise and requirement clarity.
Backlog Grooming - The Importance of Good Grooming HabitsIan Garrison
The document discusses backlog grooming meetings, which are meetings held by the product owner, scrum master, development team, and other stakeholders to prepare stories in the product backlog for upcoming sprints. It provides guidance on when and how frequently to hold grooming meetings, who should attend, and best practices for ensuring stories meet criteria for being ready to be pulled into a sprint, such as breaking down stories, using personas, and focusing on only having meaningful conversations. The goal of effective grooming is to provide transparency and predictability for the team while reducing rework.
The document discusses different approaches to estimation in waterfall and Scrum methodologies. In Scrum, teams estimate their own work in story points, which are relative units based on size and complexity. Story points help drive cross-functional behavior and do not decay over time. Ideal days estimates involve determining how long a task would take with ideal conditions and no interruptions. Planning poker uses story point cards to facilitate discussion and reach consensus on estimates. Release planning in Scrum involves estimating velocity over sprints to determine how many product backlog items can be completed.
This document discusses software development methodologies and estimating work. It provides biographical information about the author, including their experience in agile coaching and teaching. It then explores debates around estimating work, noting that estimates are not deadlines and focusing on understanding systems and accepting variability. Various estimation techniques are presented like planning poker, story points and lead time. A real case study example is shared how moving away from estimates to continuous delivery improved outcomes. The document emphasizes that #NoEstimates can work if work is done incrementally and rapidly to deliver value.
My main goal is to share and make you experiment some of the techniques that I use when transforming teams into high-perfoming agile teams, by providing you with four (4) different ways to estimate projects in Agile.
Estimating is hard to get right;
Why is estimating hard to get right?;
Why do we need to estimate;
Agile estimating and planning;
Determine the teams velocity;
Identify features and stories;
Define stories or features;
Planning Poker;
Agile Release Plan;
What if you don’t know the teams velocity?;
Estimating from ideal team structure;
The effect of rework;
Proposals and SOW’s;
The document discusses the Quality Assurance Institute (QAI), an organization that offers various software certifications. It describes QAI's history and purpose, provides details on its certification programs in software quality, testing, project management, and other areas. For each certification, it outlines the prerequisites, exam requirements, and value of being certified. The document aims to explain QAI's certifications and how professionals can prepare to obtain them.
This document discusses how agility and quality can be balanced in software development. It provides an overview of software quality concepts and metrics. It then discusses the evolution of software delivery to increasingly focus on rapid releases, high availability, and good user experience. Different types of software like systems of engagement, record, and automation are discussed. The remainder of the document outlines agile principles and practices for software delivery, testing, environments, requirements gathering, development lifecycles, and ensuring software quality in an agile process through principles like automation, continuous delivery, and feedback loops.
The document discusses testing without formal requirements. It notes that testers often complain about a lack of adequate requirements, but still rely on requirements to base their tests. Even without defined requirements, testers can ask questions about the system, anticipate common risks, involve users in acceptance testing, and perform random testing. The document provides suggestions for growing a "system function tree" to understand and describe a system without formal requirements in order to develop a test strategy, approach, and cases. It emphasizes that testing can still be done effectively even without traditional requirements.
This document discusses how quality professionals can better communicate with senior management to gain their support for quality initiatives. It suggests focusing on business metrics that matter to management like revenue, profit, customer satisfaction and retention. The document recommends quality teams map their goals to these "business influencers" and take ownership of delivery processes. It also advocates investing in innovation, building strong communication channels, and assembling a team fully committed to quality.
The document discusses quality management in the business process outsourcing (BPO) industry. It defines quality, outlines the need for quality in BPO due to increased competition and customer expectations. It describes key quality dimensions like reliability, tangibles, conformance, responsiveness, flexibility, security, and assurance. It also discusses tools that BPO companies use to achieve quality like ISO 9000 and Six Sigma. Additionally, it highlights how Indian BPO vendors emphasize quality assurance and differentiate themselves in the industry through standards and certifications.
The document provides guidance on developing and implementing effective quality programs. It discusses reviewing processes, defining organizational purpose and commitment to quality, developing change management plans, focusing quality initiatives, providing training, using measurement and feedback, and making continuous improvements. Key factors for success include visible leadership, focus, training employees, effective measures, and creating a positive work environment.
The document discusses software quality management and outlines five units: introduction to software quality; software quality assurance; quality control and reliability; quality management systems; and quality standards. It defines quality, discusses hierarchical models of quality including those proposed by Boehm and McCall, and explains techniques for improving software quality like metrics, reviews, and standards.
This document provides an introduction to Scrum, an agile framework for project management. It discusses the principles of agile development and Scrum, including self-organizing cross-functional teams, short sprint cycles, daily stand-ups, product backlogs and user stories, estimation techniques, and retrospectives for continuous improvement. The Scrum framework emphasizes empiricism, adaptation, transparency, inspection, and frequent delivery of working software.
The document repeatedly lists the URL www.TheLeadershipHub.com over multiple lines without any other text or context. It can be summarized as a document that solely contains the repeated listing of a single website URL address.
Qualitative and quantitative methods of researchJordan Cruz
The document compares and contrasts qualitative and quantitative research methods. It discusses that qualitative research aims to understand social interactions through smaller, non-randomly selected samples, while quantitative research seeks to test hypotheses and make predictions using larger, randomly selected samples and specific variables. It also outlines the different types of data collected, forms of analysis, roles of researchers, and final reporting structures between the two methods.
Introduction to Agile software testing - The 5th seminar in public seminar series from KMS Technology which have been delivering from 2011 in every two months
Scrum is an agile project management framework that focuses on iterative development, self-organizing teams, and frequent inspection points. The key aspects of Scrum include roles like the product owner, Scrum master, and self-organizing development team. Events in Scrum include sprint planning meetings, daily stand-ups, sprint reviews, and retrospectives. Artifacts include the product backlog, sprint backlog, and definition of done. Scrum aims to deliver working software frequently through short iterations called sprints.
Scrum is an agile framework for managing projects. It utilizes short development cycles called sprints to incrementally deliver working software. Key aspects of Scrum include sprint planning meetings, daily stand-up meetings, product backlogs prioritized by business value, and sprint reviews and retrospectives. The framework defines roles of the Product Owner, Scrum Master, and Development Team.
The document discusses Scrum practices at Nucleus, a company following Agile principles. It describes how Nucleus uses Scrum ceremonies like daily standups and sprints. It notes the benefits of using tools to support continuous integration, tracking metrics, and managing backlogs and defects. However, it also discusses potential risks if quality practices like testing are not properly implemented. The presentation aims to showcase Nucleus' Agile practices and tools while also highlighting areas that require attention to fully achieve Agile principles.
This document provides an introduction to the Scrum framework for agile software development. It describes Scrum roles like the Product Owner, Scrum Master, and self-organizing team. It outlines Scrum ceremonies like sprint planning, daily stand-ups, sprint reviews, and retrospectives. It also discusses the product and sprint backlogs and how teams work in sprints to deliver working software increments every 2-4 weeks using the Scrum framework.
Solving Agile Project Management Challenges with TeamPulseAbhishek Kant
This document provides an overview and agenda for a webinar on agile development with Telerik TeamPulse. The agenda covers Scrum planning in Sprint 0, an introduction to agile and Scrum in Sprint 1, the Scrum process in Sprint 2, Scrum metrics in Sprint 3, and a summary and Q&A in Sprints 4 and 5. The webinar discusses setting up a project in TeamPulse, capturing requirements, sprint and release planning, daily stand-ups, time tracking, testing, and reviews.
This document provides an introduction to agile principles and Scrum methodology. It defines key Scrum roles like Product Owner and Scrum Master. It also explains common Scrum ceremonies such as sprint planning, daily stand-ups, sprint reviews and retrospectives. Artifacts like the product backlog, sprint backlog and burn down charts are also described. The document aims to give trainees an overview of agile and Scrum concepts to help them apply these principles.
This document provides an overview of Scrum and its key concepts. It introduces Scrum as an Agile methodology used to manage product development. The document outlines the Scrum process including sprints, daily stand-ups, sprint planning and reviews. It describes Scrum roles like Product Owner and Scrum Master and artifacts like the product and sprint backlogs. Charts are presented to track work like burndowns and velocity. The document aims to explain how Scrum can help teams adapt to change and deliver working software frequently.
This document discusses customizing the Scrum process for a startup company. It describes the author's experience being assigned the Product Owner and Scrum Master roles without previous Scrum experience. The author learned Scrum and implemented it in their own way for their company. The document then provides an overview of key Scrum concepts like sprints, product backlogs, daily standups, sprint reviews, and retrospectives. It also discusses tools that can be used to support the Scrum process.
This document discusses how to work with a Scrum organization as a client. It outlines the key roles in Scrum - Product Manager, Scrum Master, and cross-functional team. It describes the Scrum process, including meetings, artifacts, and metrics used. It also discusses how Scrum-friendly contracts differ from traditional fixed schedule/budget contracts. Clients should understand the iterative nature of Scrum and work with the Product Manager as the main point of contact.
Scrum is an agile framework for managing product development. It involves short development iterations called sprints (typically 2-4 weeks) where self-organizing cross-functional teams work to deliver a potentially shippable product increment. Key aspects of scrum include product backlogs to define features, sprint planning meetings, daily stand-up meetings, sprint reviews, and retrospectives. Scrum aims to improve transparency, inspection, and adaptation and enables rapid delivery of valuable software through an empirical process that promotes continuous improvement.
This document provides an overview of the basics of Scrum, an agile project management framework. It defines key Scrum concepts like roles, activities, artifacts and processes. The document outlines that Scrum is a simple, flexible approach to managing complex projects that focuses on clarity, inspection and adaptation through short iterations and daily stand-ups. It emphasizes delivering working software frequently in sprints and adapting the backlog based on feedback.
Scrum is a framework for developing new products that allows teams to create their own lightweight process. It emphasizes empiricism, self-organization, collaboration, prioritization, and rhythm. Scrum works best for complex problems like new product development and knowledge work. Teams of 3-7 people work in short cycles called sprints to deliver working software. They plan, execute, and reflect at the end of each sprint to continuously improve.
The document discusses Agile methodology for software development. It defines Agile as being marked by readiness for change and adaptability. The key aspects of Agile include iterative development with short cycles of planning, execution and feedback. The document outlines the Agile manifesto which values individuals, working software, customer collaboration and response to change over processes, documentation, contracts and strict plans. It describes the Scrum process and challenges to adopting Agile practices.
The document provides an introduction to Agile development using Scrum. It discusses traditional software project failures and limitations of the Waterfall model. Scrum is then introduced as a framework that uses short Sprints, daily stand-up meetings, sprint reviews and retrospectives. Key Scrum roles include the Product Owner, Scrum Master and self-organizing cross-functional Team.
Using Agile to move from info centric to user centric
Managing Scope Time Cost And Team In Agile
1. Managing Scope, Time, Cost and Team in Agile
Madhu Expedith
PMP®, CSM, CSQA, ISTQB-CTFL, ITIL v3.0
Principal Consultant, Infosys Limited
2. Agenda
Part 1:
• Responding to change over following a plan
• Overview of Scrum Framework
Part 2:
• Revisit PMBOK Process Groups and Knowledge Areas
• Managing Scope, Time, Cost and Team in Scrum and
alignment with PMBOK
• Q&A Session
Slide 2
3. Responding to change over following a plan
For Discussion:
Can project teams respond to changes in the most efficient manner within
budgeted cost and desired quality?
Slide 3
5. Overview of Scrum Framework – 3-4-3
3 Roles For Discussion:
• Product Owner What are the responsibilities of a traditional
Project Manager?
• ScrumMaster
• Scrum Development Team
4 Ceremonies
• Sprint Planning Meeting
• Daily Scrum / Standup
• Sprint Review Meeting
• Sprint Retrospective
High
3 Artifacts Priority
• Product Backlog
• Release Backlog
• Sprint Backlog Low
Priority
• Sprint Burndown Product Backlog
Slide 5
6. Overview of Scrum Framework – Sprint Planning
• What is a Product Backlog?
• What are User Stories?
As a < role > I want to < action / function > so that I can
<justification / objective>. This story is done when…
< List acceptance criteria >
• Sprint Planning
• 3 Cs: Card, Conversation and Confirmation
• Story Point Estimation
• Sprint Backlog Items broken down into Sprint Tasks
• Team Commitment
• The importance of having a conversation
For Discussion:
Interpret the following statement:
“Mary had a little lamb”
Slide 6
7. Overview of Scrum Framework – Daily Scrum
• Daily Standup
• 15 mins
• Not a Status Meeting
• Team Synchronization
• Best Practice
• What did I do yesterday?
• What am I planning to do today?
• What are my impediments?
• Task Board
Slide 7
8. Overview of Scrum Framework – Sprint Review
• Sprint review
• Demonstrate working
product
• Show and tell
• Mini UAT at the end of
each sprint
• Accept items that are
“done”
• Return incomplete
items to the Product
Backlog
• Velocity
• Running average of
accepted story points
• Fixed Team
• Fixed Sprint Duration
Slide 8
9. Overview of Scrum Framework – Sprint Retrospective
Sprint
Retrospective
• Team
Reflection
• Process
Reflection
• What worked
well
• What did not
work well
• Not a post-
mortem
Slide 9
10. Scope, Time, Cost and Team (Human Resource)
Waterfall Agile
Scope Time Scope Time
Cost Team Cost Team
What is fixed?
11. PMBOK Process Groups and Knowledge Areas
Process Groups Initiating Planning Executing Monitoring & Closing
Knowledge Areas Control
Project Integration
Management
Project Scope Management
Project Time Management
Project Cost Management
Project Quality Management
Project Human Resource
Management
Project Communications
Management
Project Risk Management
Project Procurement
Management
12. Managing Scope
• Requirements: User Stories
/ Product Backlog Items in
the Product Backlog
• Iterative planning (scope for
the sprint)
• Fixed team that is self-
organizing and cross-
functional
• Scope frozen within the
sprint
• No Change Requests!
Slide 12
13. Managing Time
• Time is fixed – all activities
are time-boxed
• Sprint Planning
• Sprint Backlog Items
broken down into Sprint
Tasks
• Team capacity based
planning
• Release Planning and
Scheduling
Slide 13
15. Managing Team
• Fixed team
• Co-location preferred
• Self-organizing
• Cross-functional
Slide 15
16. The Agile Manifesto and the Principles behind Agile Manifesto
Agile Manifesto Principles behind Agile Manifesto
1. Individuals and 1. Our highest priority is to satisfy the customer through early and
interactions over continuous delivery of valuable software.
processes and tools 2. Welcome changing requirements, even late in development. Agile
processes harness change for the customer's competitive advantage.
2. Working software over 3. Deliver working software frequently, from a couple of weeks to a
comprehensive couple of months, with a preference to the shorter timescale.
documentation 4. Business people and developers must work together daily throughout
the project
3. Customer collaboration 5. Build projects around motivated individuals. Give them the
over contract environment and support they need, and trust them to get the job
negotiation done.
4. Responding to change 6. The most efficient and effective method of conveying information to
and within a development team is face-to-face conversation.
over following a plan
7. Working software is the primary measure of progress.
That is, while there is value in 8. Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace
the items on the right, we indefinitely.
value the items on the left
more. 9. Continuous attention to technical excellence and good design
enhances agility.
10. Simplicity--the art of maximizing the amount of work not done--is
essential.
11. The best architectures, requirements, and designs emerge from self-
organizing teams.
12. At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.
Slide 16