Scrum, Kanban, and Scrumban are agile frameworks discussed. Scrum uses sprints, daily stand-ups, and retrospectives, with a product backlog and sprint backlog mapped to a scrum board. Kanban uses a process board to visualize workflow and work in progress (WIP) limits. Scrumban combines elements of Scrum and Kanban, using a board to map work continuously while also having sprints, stand-ups and retrospectives.
The aim of agile methods is to reduce overheads in the software process (e.g. by limiting documentation) and to be able to respond quickly to changing requirements without excessive rework.
This presentation is about Scrum methodology. First it reviewed traditional SDM and then talk about Agile and Scrum
Scrum is an agile software development framework that focuses on self-organizing cross-functional teams, sprints of work lasting 2-4 weeks, daily stand-up meetings, and empirical process control. The key roles are the Product Owner who prioritizes features, the Scrum Master who facilitates the process, and the self-organizing Development Team. Scrum uses sprints, daily scrums, sprint planning meetings, sprint reviews, and retrospectives to deliver working software frequently in an iterative and incremental fashion.
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.
It's not Scrum VS. Kanban! It is Scrum AND Kanban!Mahesh Singh
Kanban does not compete with Scrum. Kanban can be applied by Scrum teams to improve and address issues they might be facing with their development processes. Far too often, Kanban gets positioned as a replacement for Scrum, when it can really be a powerful tool for Scrum teams to improve their overall delivery capability!
This document provides an introduction to agile frameworks like Scrum and Kanban. It defines key Scrum terms and ceremonies such as the product backlog, sprints, daily stand-ups, and retrospectives. Kanban concepts discussed include limiting work-in-progress, measuring lead time and flow, and using kanban boards to visualize workflow. The document compares Scrum and Kanban, noting when each approach is generally best suited. It also offers tips for analyzing processes using kanban principles like identifying bottlenecks and impediments.
The document provides an overview of the Agile Scrum methodology. It describes that Agile is an iterative process involving constant collaboration with stakeholders. Scrum is an Agile framework that breaks work into sprints with daily stand-ups. Key Scrum roles include the Product Owner who manages the backlog, the Scrum Master who removes impediments, and the Development Team who delivers increments each sprint. Artifacts include the Product and Sprint Backlogs, the Definition of Done, and the increment delivered at the end of each sprint.
EHS Conducted SCRUM Overview Session for a Corporate Company in Lahore covering Basics i.e. What is Agile & Scrum, Why to use Scrum, Benefits, Values, Artifacts, Events, Scrum Teams & Roles...
Scrum vs Kanban - Which Agile Methodology Fits Best For Your Team?Invensis Learning
Scrum vs Kanban? Which fits best for your team? Learn the key differences between the two popular Agile frameworks, Scrum and Kanban. Also, learn when to use these two Agile Methodologies.
https://www.youtube.com/watch?v=pxxmSLJj8FQ&t=435s
The aim of agile methods is to reduce overheads in the software process (e.g. by limiting documentation) and to be able to respond quickly to changing requirements without excessive rework.
This presentation is about Scrum methodology. First it reviewed traditional SDM and then talk about Agile and Scrum
Scrum is an agile software development framework that focuses on self-organizing cross-functional teams, sprints of work lasting 2-4 weeks, daily stand-up meetings, and empirical process control. The key roles are the Product Owner who prioritizes features, the Scrum Master who facilitates the process, and the self-organizing Development Team. Scrum uses sprints, daily scrums, sprint planning meetings, sprint reviews, and retrospectives to deliver working software frequently in an iterative and incremental fashion.
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.
It's not Scrum VS. Kanban! It is Scrum AND Kanban!Mahesh Singh
Kanban does not compete with Scrum. Kanban can be applied by Scrum teams to improve and address issues they might be facing with their development processes. Far too often, Kanban gets positioned as a replacement for Scrum, when it can really be a powerful tool for Scrum teams to improve their overall delivery capability!
This document provides an introduction to agile frameworks like Scrum and Kanban. It defines key Scrum terms and ceremonies such as the product backlog, sprints, daily stand-ups, and retrospectives. Kanban concepts discussed include limiting work-in-progress, measuring lead time and flow, and using kanban boards to visualize workflow. The document compares Scrum and Kanban, noting when each approach is generally best suited. It also offers tips for analyzing processes using kanban principles like identifying bottlenecks and impediments.
The document provides an overview of the Agile Scrum methodology. It describes that Agile is an iterative process involving constant collaboration with stakeholders. Scrum is an Agile framework that breaks work into sprints with daily stand-ups. Key Scrum roles include the Product Owner who manages the backlog, the Scrum Master who removes impediments, and the Development Team who delivers increments each sprint. Artifacts include the Product and Sprint Backlogs, the Definition of Done, and the increment delivered at the end of each sprint.
EHS Conducted SCRUM Overview Session for a Corporate Company in Lahore covering Basics i.e. What is Agile & Scrum, Why to use Scrum, Benefits, Values, Artifacts, Events, Scrum Teams & Roles...
Scrum vs Kanban - Which Agile Methodology Fits Best For Your Team?Invensis Learning
Scrum vs Kanban? Which fits best for your team? Learn the key differences between the two popular Agile frameworks, Scrum and Kanban. Also, learn when to use these two Agile Methodologies.
https://www.youtube.com/watch?v=pxxmSLJj8FQ&t=435s
The document provides an overview of the Scrum model for agile software development. Scrum divides projects into short sprints of 2-4 weeks to focus development. It utilizes daily stand-up meetings, sprint planning and reviews, and retrospectives. Key roles include the product owner who prioritizes the backlog, the scrum master who facilitates the process, and the cross-functional development team. Scrum aims to provide structure while allowing for flexibility, feedback and adapting to changes.
Agile is an iterative process that emphasizes frequent inspection and adaptation. The Agile Manifesto values individuals and interactions, working software, customer collaboration, and responding to change over processes, tools, contracts, and following a plan. Common Agile methodologies include Scrum, Extreme Programming (XP), Lean, Kanban, Feature-Driven Development (FDD), Dynamic Systems Development Method (DSDM), and Crystal. Scrum uses sprints, daily stand-ups, and artifacts like product backlogs and increments. XP focuses on simplicity, feedback, and pair programming. Lean aims to eliminate waste. Kanban uses visual boards and limits work-in-progress. FDD develops features incrementally. DSDM prioritizes
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.
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.
Agile processes like Scrum are needed because software development is complex and requirements often change. Scrum is an agile framework that uses short cycles ("sprints") to incrementally develop products. Key Scrum roles include the Product Owner, Scrum Master, and Team. The Product Owner manages product requirements and priorities. The Scrum Master facilitates the process. The Team does the work. Main Scrum artifacts are the Product Backlog, Sprint Backlog, and Product Increment. The Scrum process involves Sprint Planning, Daily Stand-ups, Sprint Review, and Retrospectives to continuously improve.
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
The document discusses Agile software development methodologies, with a focus on Scrum. It defines Agile as iterative development methods that promote adaptation over planning. Scrum is described as the most commonly used Agile framework, involving short development cycles called sprints, daily stand-up meetings, and product backlogs to track work. The key roles in Scrum include the Product Owner, Development Team, and Scrum Master.
- 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.
Scrum vs Kanban: Is there really a battle?Flavius Stef
The document compares and contrasts Scrum and Kanban frameworks. It discusses the mechanics of each approach, such as sprint planning and limiting work-in-progress in Kanban. The document also explores hybrid approaches like Scrumban and how teams can take principles from different frameworks to tailor their process. Overall, the focus is on understanding the similarities and differences between Scrum and Kanban to determine the best fit for a given team or project.
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
Scrum is an agile project management framework that emphasizes iterative development, self-organizing cross-functional teams, and regular inspection of progress and redirection of efforts. Key aspects of Scrum include dividing work into sprints (typically 2-4 weeks), daily stand-up meetings, and artifacts like the product backlog, sprint backlog, and increment. The core roles are the product owner, scrum master, and development team. The product owner manages the product backlog, the scrum master facilitates the process, and the development team does the work.
The document discusses Scrum, an agile framework for managing product development. It describes key Scrum concepts like sprints, daily stand-ups, product and sprint backlogs, and roles like the Scrum Master and Product Owner. Scrum uses short development cycles called sprints to incrementally deliver working software. Teams self-organize during sprints to progress features on the product backlog.
The document provides an overview of Agile methodology and Scrum framework. It describes that Agile is an alternative project management approach that uses short iterative cycles called sprints to incrementally deliver working software. Scrum is the most commonly used Agile framework and involves roles of Product Owner, Scrum Master, and team. It uses artifacts like Product Backlog and Sprint Backlog and events like Sprint Planning, Daily Scrum, and Sprint Review.
This document provides an overview and comparison of the agile methodologies Scrum, Kanban, and Scrumban. It defines each methodology, noting that Scrum uses iterative sprints to complete tasks from a backlog, Kanban uses a pull system and limits work-in-progress to identify bottlenecks, and Scrumban combines elements of Scrum and Kanban. While each has strengths, the document concludes that the best approach depends on the specific needs and environment of the project.
This document provides an overview of Scrum training. It introduces the trainer, Deniz Gungor, and their background. It then outlines the agenda, which will cover Scrum fundamentals, a Scrum simulation game, and the Scrum framework. Key aspects of Scrum are defined, including self-organizing Scrum teams, iterative delivery, the Product Owner, Scrum Master, Development Team, events like the Daily Scrum and Sprint Review, and artifacts like the Product Backlog and Sprint Backlog. The training will help participants understand and apply the Scrum framework to projects.
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 is an agile framework for managing product development projects. It utilizes short "sprints" where self-organizing cross-functional teams work to complete user stories from a prioritized backlog. Daily stand-up meetings help coordinate work. At the end of each sprint, teams demonstrate completed work to stakeholders for feedback to improve subsequent sprints. Periodic retrospectives help teams improve their processes. Compared to traditional "waterfall" models, Scrum aims to handle changing requirements better through rapid iteration and continuous customer input.
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.
Training - Introducing Agile, Lean and KanbanSudipta Lahiri
This is a presentation that I did for a team to introduce them to Agile, Lean and Kanban, It covers these these 3 areas, how they overlap and then gets into greater details about the Kanban Method.
The document provides an overview of the Scrum model for agile software development. Scrum divides projects into short sprints of 2-4 weeks to focus development. It utilizes daily stand-up meetings, sprint planning and reviews, and retrospectives. Key roles include the product owner who prioritizes the backlog, the scrum master who facilitates the process, and the cross-functional development team. Scrum aims to provide structure while allowing for flexibility, feedback and adapting to changes.
Agile is an iterative process that emphasizes frequent inspection and adaptation. The Agile Manifesto values individuals and interactions, working software, customer collaboration, and responding to change over processes, tools, contracts, and following a plan. Common Agile methodologies include Scrum, Extreme Programming (XP), Lean, Kanban, Feature-Driven Development (FDD), Dynamic Systems Development Method (DSDM), and Crystal. Scrum uses sprints, daily stand-ups, and artifacts like product backlogs and increments. XP focuses on simplicity, feedback, and pair programming. Lean aims to eliminate waste. Kanban uses visual boards and limits work-in-progress. FDD develops features incrementally. DSDM prioritizes
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.
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.
Agile processes like Scrum are needed because software development is complex and requirements often change. Scrum is an agile framework that uses short cycles ("sprints") to incrementally develop products. Key Scrum roles include the Product Owner, Scrum Master, and Team. The Product Owner manages product requirements and priorities. The Scrum Master facilitates the process. The Team does the work. Main Scrum artifacts are the Product Backlog, Sprint Backlog, and Product Increment. The Scrum process involves Sprint Planning, Daily Stand-ups, Sprint Review, and Retrospectives to continuously improve.
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
The document discusses Agile software development methodologies, with a focus on Scrum. It defines Agile as iterative development methods that promote adaptation over planning. Scrum is described as the most commonly used Agile framework, involving short development cycles called sprints, daily stand-up meetings, and product backlogs to track work. The key roles in Scrum include the Product Owner, Development Team, and Scrum Master.
- 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.
Scrum vs Kanban: Is there really a battle?Flavius Stef
The document compares and contrasts Scrum and Kanban frameworks. It discusses the mechanics of each approach, such as sprint planning and limiting work-in-progress in Kanban. The document also explores hybrid approaches like Scrumban and how teams can take principles from different frameworks to tailor their process. Overall, the focus is on understanding the similarities and differences between Scrum and Kanban to determine the best fit for a given team or project.
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
Scrum is an agile project management framework that emphasizes iterative development, self-organizing cross-functional teams, and regular inspection of progress and redirection of efforts. Key aspects of Scrum include dividing work into sprints (typically 2-4 weeks), daily stand-up meetings, and artifacts like the product backlog, sprint backlog, and increment. The core roles are the product owner, scrum master, and development team. The product owner manages the product backlog, the scrum master facilitates the process, and the development team does the work.
The document discusses Scrum, an agile framework for managing product development. It describes key Scrum concepts like sprints, daily stand-ups, product and sprint backlogs, and roles like the Scrum Master and Product Owner. Scrum uses short development cycles called sprints to incrementally deliver working software. Teams self-organize during sprints to progress features on the product backlog.
The document provides an overview of Agile methodology and Scrum framework. It describes that Agile is an alternative project management approach that uses short iterative cycles called sprints to incrementally deliver working software. Scrum is the most commonly used Agile framework and involves roles of Product Owner, Scrum Master, and team. It uses artifacts like Product Backlog and Sprint Backlog and events like Sprint Planning, Daily Scrum, and Sprint Review.
This document provides an overview and comparison of the agile methodologies Scrum, Kanban, and Scrumban. It defines each methodology, noting that Scrum uses iterative sprints to complete tasks from a backlog, Kanban uses a pull system and limits work-in-progress to identify bottlenecks, and Scrumban combines elements of Scrum and Kanban. While each has strengths, the document concludes that the best approach depends on the specific needs and environment of the project.
This document provides an overview of Scrum training. It introduces the trainer, Deniz Gungor, and their background. It then outlines the agenda, which will cover Scrum fundamentals, a Scrum simulation game, and the Scrum framework. Key aspects of Scrum are defined, including self-organizing Scrum teams, iterative delivery, the Product Owner, Scrum Master, Development Team, events like the Daily Scrum and Sprint Review, and artifacts like the Product Backlog and Sprint Backlog. The training will help participants understand and apply the Scrum framework to projects.
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 is an agile framework for managing product development projects. It utilizes short "sprints" where self-organizing cross-functional teams work to complete user stories from a prioritized backlog. Daily stand-up meetings help coordinate work. At the end of each sprint, teams demonstrate completed work to stakeholders for feedback to improve subsequent sprints. Periodic retrospectives help teams improve their processes. Compared to traditional "waterfall" models, Scrum aims to handle changing requirements better through rapid iteration and continuous customer input.
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.
Training - Introducing Agile, Lean and KanbanSudipta Lahiri
This is a presentation that I did for a team to introduce them to Agile, Lean and Kanban, It covers these these 3 areas, how they overlap and then gets into greater details about the Kanban Method.
This document summarizes a presentation on a cross-disciplinary watershed management project. The project aims to integrate biophysical and social factors to better target management practices. It develops a diagnostic decision support system to identify areas exporting high pollutant levels ("critical source areas") and prescribe targeted best management practices (BMPs). Modeling evaluates how climate change may increase polluted areas and impact BMP effectiveness. Interviews identify competing views between scientists and farmers on water issues. The work seeks to overcome divergent stakeholder perspectives and better engage communities in watershed management.
This study examined the impact of on-site wastewater treatment (septic) systems on water quality and quantity in urbanizing watersheds in metro Atlanta, GA. The results showed that septic system density above 100 units/km2 was correlated with higher levels of fecal indicator bacteria and nitrates in streams, especially in spring. A survey found residents were willing to pay to upgrade septic systems to improve water quality. The study concluded that septic systems increase total watershed water yield, especially during dry periods, and recommended education programs to increase awareness of septic system impacts.
This document provides an introduction and tutorial to using PowerShell. It begins by discussing PowerShell's purpose as a scripting language for "gluing" existing components together rather than for low-level programming. The tutorial then demonstrates basic PowerShell concepts like variables, arrays, input/output, conditions, iteration, and functions. It also introduces regular expressions and their special characters. The document is intended to get readers started with PowerShell's basic programming constructs.
This research aims to identify the most cost-effective combination of upland, riparian, and in-stream conservation practices to reduce sediment loads in the Fort Cobb watershed. Research includes modeling erosion under different land management scenarios and surveying stakeholders. Preliminary results show streambank erosion contributes significantly to sediment loads. Field studies quantified streambank erodibility, which varies within the watershed. Process-based models are being used to predict streambank erosion at site and reach scales. Landowner surveys found enrollment in conservation programs increases with farm revenue, education, and stewardship mindsets.
This document summarizes a project that evaluated strategies for agricultural water conservation in the Colorado River Basin. The project had four objectives: 1) Evaluate available conservation technology; 2) Identify legal, economic, and social barriers; 3) Strategize with producers and managers to overcome barriers; and 4) Share findings. Case studies were conducted on innovative collaboration programs. Meetings with producers explored barriers like "use it or lose it" laws. The project concluded that one-size-fits-all solutions are unlikely, and that addressing institutional and economic barriers can benefit farmers and help sustain agriculture in the basin.
This document summarizes research on applying phosphate isotopes to trace sources and cycling of phosphorus in East Creek, a watershed in the Chesapeake Bay region. It discusses:
1) Phosphorus and high phytate levels in East Creek. Phytate is a major storage form of phosphorus found in plant materials.
2) Measuring oxygen isotopes in phosphate to track the original source of phytate as it is degraded by enzymes. Different enzymes fractionate isotopes in unique ways, allowing identification of active enzymes.
3) Phytate promotes the proliferation of microorganisms that can degrade it. Understanding phytate cycling provides insights into managing phosphorus pollution in
'Sound-bites' are the useful takeaways or narrative fragments from conversations and presentations. When we only hear the 'sound-bites', we lose valuable information and will end up with poor outcomes.
This session will explore the typical reactions that we get to our 'sound-bite' rallying cries like 'Celebrate Failure'. The reactions vary from the hoped for enthusiastic embrace all the way to disappointing disengagement...where our colleagues treat us as foolish for suggesting such a thing could be good in their workplace. These reactions are what we leave behind and the enthusiastic embrace can be just as harmful as the disappointing disengagement – in some ways the former is more dangerous and we need to be careful that what we leave behind does not cause any damage.
We will unpack 'celebrate failure' and explain a healthier way to interpret the intention behind the 'sound-bite' as a means to explore boundaries in complex systems.
History shows us that people with the best intentions can be misunderstood and many years later treated as creators of our current woes, an example being The Principles of Scientific Management by F.W. Taylor. In 100 years, what will people think of Lean and Agile? If we take another look, we can see a pattern emerging where Scientific Management can identify Best Practices in the Obvious Domain, Systems Thinking applies nicely in the Complicated Domain and the concepts of probe, sense and respond allow us to explore complexity more effectively.
By using the modern 'Celebrate Failure' example and lessons from history, this session will remind us all to be careful with what we leave behind in every conversation.
10 Agile Take-Aways for Senior ManagementDonald Ewart
This document provides an introduction to agile for management. It summarizes 10 key takeaways about agile, including that software development is complex, empirical processes can find better solutions, agile is an umbrella term, and estimates in a complex world cannot be precise. It also notes that delay is the biggest cost, agile manages scope, uses feedback to navigate complexity, and empowers product management through points of stability. The document concludes that effective deliveries come from trusted, empowered teams and that agile moves work to the people.
Business Agility - the Ability to Gain from Continuous ChangeFranky Redant
This document discusses the concept of VUCA and business agility. It defines VUCA as volatility, uncertainty, complexity and ambiguity. It then discusses different frameworks for understanding change like the Cynefin framework. It provides definitions of business agility focusing on adaptability, flexibility and balance. It outlines different domains of agility from the organization level down to teams. Finally, it proposes a new definition of business agility as "the ability to improve/gain from continuous change."
Yes, we all know the world has gone VUCA (Volatile, Uncertain, Complex and Ambiguous). But even within the Agile movement, deep inside, we still like to stick to an idea of management which is attached to concepts such as predictability, systematization, repeatability, and tries to make reality fit to this mindset.
Based on Dave Snowden’s Cynefin Framework, and in partnership with his company, we are at the moment developing a set of practical methods and tools that allow managers from, the team leader upwards to master the complex aspects of reality. This paper gives you insight into our ongoing work.
The document discusses the importance and benefits of conversation. It notes that conversation is creative and can lead to new ideas being formed from recombining existing ideas. Conversation improves cognitive functions like working memory and focus. Bringing diverse groups of people together in conversation can boost collective intelligence and drive innovation, as new connections and ideas are made. Some ways to foster productive conversation mentioned include using online tools, holding meetings that encourage equal participation, and creating spaces like cafes for knowledge sharing.
This document discusses knowledge work and organizational learning through the lens of several frameworks. It proposes a Process Learning Cycle (PLC) model to describe how knowledge moves through an organization from a program manager to executive approval. The PLC is analyzed using concepts from Boisot's information space model and Core Group Theory to understand how power and different types of knowledge are amplified at different stages. Dynamics between explicit and tacit knowledge exchanges are also examined using Nonaka's SECI model and the document proposes a typology of information to understand gains and losses of knowledge.
How cynefin model improves lean implementationPierre E. NEIS
The document discusses how the Cynefin model can improve lean implementation. It provides an overview of the Cynefin framework, which categorizes systems as simple, complicated, complex, or chaotic. This helps tailor leadership approaches and process improvement methods. The Cynefin model supports lean tools by assessing whether a situation requires directive changes or emergent solutions. It can help design effective processes for 5S, waste reduction, PDCA cycles, and other lean best practices. Overall, Cynefin provides a systematic approach to continuous improvement that considers the dynamics of each situation.
The document discusses expanding on the Cynefin knowledge framework by exploring additional domains and transitions between domains. It proposes adding "ambiguous," "affirmative," and "emergent" domains. It also discusses different types of coherence that can occur between domains, such as intentional, dispositional, and retrospective coherence. Further, it examines how knowledge is formed through interactions between domains like moving from critique to emergence.
This talk given at MeetMagento Poland 2014 presents my experience with doing Agile development and its challenges on development vs support projects. It will be a practical approach to project management, with how Agile can be applied inside a modern web development agency. Talk covers resource assignment, Scrum, Kanban, developer empowerment and continuous delivery with client satisfaction.
The document discusses Scrum, an agile framework for project management. It describes some issues with traditional waterfall models like high risks and uncertainty. Scrum aims to address these issues by allowing for frequent delivery of working software, adapting to changes, and welcoming late changes. The document then outlines the key aspects of Scrum like product and sprint backlogs, daily stand-ups, sprint reviews, and retrospectives. It discusses how Scrum has been used successfully in various domains like software, games, websites, and more. Finally, it covers some benefits of Scrum from different stakeholder perspectives.
The document provides an overview of Agile project management. It discusses the history and origins of Agile, which began in 2001 when 17 software development pioneers created the Agile Manifesto. It defines Agile as an iterative approach to software delivery that builds incrementally from user stories prioritized in two-week sprints. The document outlines the key principles of Agile methodology including Scrum framework with roles of Product Owner, Scrum Master, and development team. It compares the Waterfall and Agile approaches and describes the Scrum process, artifacts, and ceremonies used in Agile development.
This document provides an overview of Agile methodologies like Scrum and Kanban. It discusses the Agile Manifesto principles of prioritizing individuals, interactions, working software, and customer collaboration over processes, tools, documentation, and contract negotiation. Core Kanban principles include visualizing work, limiting work in progress, focusing on flow, and continuous improvement. Scrum roles include the Product Owner, Scrum Master, and Scrum Team. The Product Owner represents stakeholders and users. The Scrum Master facilitates meetings and removes impediments while not having authority over the team. The Scrum Team works to deliver working software in short sprints through self-organization.
The document provides an overview of agile methodologies. It defines agile as an iterative project management approach using short development cycles called sprints. The core values of agile according to the Agile Manifesto are prioritizing individuals, working software, customer collaboration, and responding to change. Key aspects of agile include sprint planning, daily standup meetings, user stories, acceptance criteria, product and sprint backlogs, and retrospectives. Popular agile frameworks are Scrum, Kanban, and lean.
This document provides an overview of agile software development methodologies, focusing on Scrum. It describes the traditional waterfall methodology and its limitations. Agile methodologies like Scrum promote iterative development through collaboration between cross-functional teams. Scrum uses sprints, daily stand-ups, sprint reviews and retrospectives. Key roles include the product owner, Scrum master, and self-organizing development team. The product backlog and sprint backlog are key artifacts that help manage work in progress.
The role of a QA tester on a Scrum team includes:
1) Participating in sprint planning and retrospectives to provide input on testing needs and improvements.
2) Testing software increments throughout the sprint to find issues early.
3) Communicating regularly with developers through daily standups and demos.
4) Ensuring quality by developing test cases, conducting exploratory testing, and automating tests.
5) Helping clarify requirements and identify ambiguities.
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.
Agile and Scrum Overview for PMs, Designers and Developers Aaron Roy
This is an overview of the flavor of agile/scrum I had my team use at Bond in Q2 2017. We heavily emphasized the importance of having a shared language between cross-functional teams and this deck was meant as a primer that could be shared between product managers, designers, and developers.
This document discusses Agile and Scrum methodologies. It describes Scrum frameworks which include roles like Product Owner, Team and Scrum Master. It outlines Scrum meetings like Sprint Planning, Daily Scrum, Sprint Demo and Retrospective. It also describes Scrum artifacts like Product Backlog, Sprint Backlog and Burn-down Chart which help track and manage work in Scrum projects.
This document provides an introduction to agile frameworks like Scrum, XP, Lean, and Kanban. It discusses agile principles like valuing individuals, collaboration, and responding to change. It describes Scrum roles, events, and tools like user stories, burn-down charts, and daily stand-ups. XP's emphasis on testing is covered. Lean principles like eliminating waste and building quality in are explained. Kanban concepts like pull systems and work-in-progress limits are also summarized. The document concludes with recommendations for certifications and further reading on agile methods.
How to do SCRUM and how are we doing it in practice at Klarna TLV.
Covering the next topics: sprints, retro + demo, standup, pair programming, code quality, MVP, continuous integration, continuous deployment, and more...
Scrum is an agile framework that uses short iterations and frequent delivery to develop products. Some common anti-patterns that can hurt Scrum productivity include absent stakeholders at sprint planning, outdated product backlogs, teams taking on more work than they can handle, and lack of preparation or participation at important Scrum events like daily stand-ups, sprint reviews, and retrospectives. Monitoring anti-patterns through tools like sprint burndown charts and discussions at retrospective meetings can help teams improve by addressing issues and making changes.
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 document provides an overview of Scrum, including its key roles, events, artifacts, and principles. Scrum is a framework for managing complex projects that require frequent collaboration and feedback. It uses short "sprints" to incrementally develop work into a potentially shippable product increment. The core Scrum roles are the Product Owner, who manages priorities and requirements, the Development Team, who do the work, and the Scrum Master, who facilitates the process. Events include Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective. Artifacts include the Product Backlog and Sprint Backlog. The goal is to continuously improve through transparency, inspection, and adaptation each sprint.
Scrum is an agile framework for managing product development that focuses on iterative delivery of value through collaboration between self-organizing cross-functional teams. Key aspects of Scrum include short "sprints" where work is defined and tracked on a sprint backlog, daily stand-up meetings, sprint planning and review sessions, and emphasizing working software over documentation. The framework defines three roles - Product Owner who prioritizes features, Scrum Master who facilitates the process, and a self-organizing Development Team.
The document provides an introduction and overview of Agile Scrum methodology. It describes Scrum as an agile process that focuses on delivering high business value in short iterations through working software. Key Scrum roles include the Product Owner who prioritizes features, the Scrum Master who removes impediments, and cross-functional self-organizing teams. Ceremonies like Sprints, Daily Stand-ups, Sprint Reviews and Retrospectives support iterative development. Product and Sprint Backlogs track work in progress.
Wondering what Scrum is? Need a little recap? This short presentation will give you the quick rundown of scrum and what it entails as well as the best ways to use it.
This document provides an introduction to Agile and Scrum methodologies. It begins with an overview of the presenter and their experience. It then contrasts the traditional waterfall approach with Agile, noting that Agile values individuals, collaboration, working software and responding to change. The Agile manifesto principles are outlined. Scrum is introduced as an Agile framework, describing its roles, ceremonies and artifacts like sprints and product backlogs. Key Scrum concepts like user stories, estimation, and definitions of done are defined. The document concludes by noting that simply doing Agile iterations is not enough and that teams must embrace Agile values like collaboration and continual improvement.
Similar to Choosing right agile methodology for your project (20)
The Most Inspiring Entrepreneurs to Follow in 2024.pdfthesiliconleaders
In a world where the potential of youth innovation remains vastly untouched, there emerges a guiding light in the form of Norm Goldstein, the Founder and CEO of EduNetwork Partners. His dedication to this cause has earned him recognition as a Congressional Leadership Award recipient.
Best Competitive Marble Pricing in Dubai - ☎ 9928909666Stone Art Hub
Stone Art Hub offers the best competitive Marble Pricing in Dubai, ensuring affordability without compromising quality. With a wide range of exquisite marble options to choose from, you can enhance your spaces with elegance and sophistication. For inquiries or orders, contact us at ☎ 9928909666. Experience luxury at unbeatable prices.
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 INDIA SATTA MATKA MATKA TIPS MATKA WAPKA ALL MATKA RESULT LIVE ONLINE MATKA RESULT KALYAN MATKA RESULT DPBOSS MATKA 143 MAIN MATKA KALYAN MATKA RESULTS KALYAN CHART
Prescriptive analytics BA4206 Anna University PPTFreelance
Business analysis - Prescriptive analytics Introduction to Prescriptive analytics
Prescriptive Modeling
Non Linear Optimization
Demonstrating Business Performance Improvement
Starting a business is like embarking on an unpredictable adventure. It’s a journey filled with highs and lows, victories and defeats. But what if I told you that those setbacks and failures could be the very stepping stones that lead you to fortune? Let’s explore how resilience, adaptability, and strategic thinking can transform adversity into opportunity.
❼❷⓿❺❻❷❽❷❼❽ Dpboss Matka Result Satta Matka Guessing Satta Fix jodi Kalyan Final ank Satta Matka Dpbos Final ank Satta Matta Matka 143 Kalyan Matka Guessing Final Matka Final ank Today Matka 420 Satta Batta Satta 143 Kalyan Chart Main Bazar Chart vip Matka Guessing Dpboss 143 Guessing Kalyan night
Ellen Burstyn: From Detroit Dreamer to Hollywood Legend | CIO Women MagazineCIOWomenMagazine
In this article, we will dive into the extraordinary life of Ellen Burstyn, where the curtains rise on a story that's far more attractive than any script.
The APCO Geopolitical Radar - Q3 2024 The Global Operating Environment for Bu...APCO
The Radar reflects input from APCO’s teams located around the world. It distils a host of interconnected events and trends into insights to inform operational and strategic decisions. Issues covered in this edition include:
IMPACT Silver is a pure silver zinc producer with over $260 million in revenue since 2008 and a large 100% owned 210km Mexico land package - 2024 catalysts includes new 14% grade zinc Plomosas mine and 20,000m of fully funded exploration drilling.
Call8328958814 satta matka Kalyan result satta guessing➑➌➋➑➒➎➑➑➊➍
Satta Matka Kalyan Main Mumbai Fastest Results
Satta Matka ❋ Sattamatka ❋ New Mumbai Ratan Satta Matka ❋ Fast Matka ❋ Milan Market ❋ Kalyan Matka Results ❋ Satta Game ❋ Matka Game ❋ Satta Matka ❋ Kalyan Satta Matka ❋ Mumbai Main ❋ Online Matka Results ❋ Satta Matka Tips ❋ Milan Chart ❋ Satta Matka Boss❋ New Star Day ❋ Satta King ❋ Live Satta Matka Results ❋ Satta Matka Company ❋ Indian Matka ❋ Satta Matka 143❋ Kalyan Night 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 INDIA SATTA MATKA MATKA TIPS MATKA WAPKA ALL MATKA RESULT LIVE ONLINE MATKA RESULT KALYAN MATKA RESULT DPBOSS MATKA 143 MAIN MATKA KALYAN MATKA RESULTS KALYAN CHART
The Steadfast and Reliable Bull: Taurus Zodiac Signmy Pandit
Explore the steadfast and reliable nature of the Taurus Zodiac Sign. Discover the personality traits, key dates, and horoscope insights that define the determined and practical Taurus, and learn how their grounded nature makes them the anchor of the zodiac.
2. Speakers
Prabhat Sinha
He has been managing product and
project since 8 years. After work Prabhat
can be found jogging and socializing at
local parks.
Prabhat lives in the bustling city New Delhi
with his wife and 2 kids.
Shani Memfy
She’s been managing product and project
deliveries since 1999. After work you can
find her on the court shooting hoops with
a local Netball league.
Shani lives in a suburban city in Israel with
her husband and 4 children.
3. Agenda
1. What is Agile
2. Agile Frameworks
● Scrum
● KANBAN
● Scrumban
● Extreme Programming
● Lean
● Feature Driven development
3. Comparison
4. CYNEFIN
4. Better ways of developing software is by doing it and helping others do it.
Agile gives importance to:
● Individuals and interactions over processes and tools
● Working software over comprehensive documentation
● Customer collaboration over contract negotiation
● Responding to change over following a plan
What is Agile?
5. 12 Principles of Agile Manifesto
Our highest priority is
to satisfy the customer
through early and
continuous delivery of
valuable software.
Welcome changing requirements,
even late in development. Agile
processes harness change for the
customer’s competitive advantage.
Deliver working software frequently,
from a couple of weeks lo a couple
of months, with a preference to the
shorter timescale.
Business people and
developers must work
together daily
throughout the project.
Build projects around motivated
individuals. Give them the
environment & support they need,
and trust them to get the job done.
Agile processes promote
sustainable development. The
sponsors, developers, and users
should be able to maintain a
constant pace indefinitely.
Working software is
the primary measure of
progress.
The most efficient and effective
method of Conveying information
to and within a development team
is face-to-face conversation.
Continuous attention to technical
excellence and good design
enhances agility.
Simplify--the art of
maximizing the
amount of work not
done--is essential.
The best architectures,
requirements & designs
emerge from self-organizing
teams.
At regular intervals, the team
reflects on how to become more
effective, then tunes and adjusts its
behavior accordingly.
01
04
07
10
02
05
08
11
03
06
09
12
6. There are several agile project management frameworks being successfully used
for delivering Drupal projects. Let’s evaluate few popular agile frameworks:
1. Scrum
2. Kanban
3. Scrumban
4. Extreme Programming
5. Lean Development
6. Feature driven development
In next few slides we will discuss each frameworks
one by one and Help you choose the most fitting
for your projects.
Agile Is a Methodology Only
AGILE
Extreme
Programming
(XP)
Scrum
Kanban
Lean
FDD
7. against a similar group from the opposing side.Scrum doesn’t work when the team is not working to a shared goal
and push forward
An ordered formation of players, used to restart play, in which the forwards of a
team form up with arms interlocked and heads down, and push forward against a
similar group from the opposing side.No distractions
Scrum
Scrum is an Agile framework that brings order to chaos.
Scrum comes from Rugby:
An ordered formation of players used to restart play
in which the forwards of a team form up with arms interlocked
and heads down,
The cross functioning team Sprint
PO, SM &
the team
8. Scrum in a Nutshell
The project requirements
● Clear vision of the end
product
● A clear set of requirements
(user stories)
○ Product Backlog at
least for the upcoming
2 sprints
● Objective to add small
marketable values in each
increment
○ PSP: potentially
shippable product
○ MMF: minimal
marketable feature
The Team
Product Owner, Scrummaster and
Team
● Well-trained
● Specialized
● Capable of Self-management
● Communicative
● Ability to Make Decisions
● Common Goal
● Self Improving
Processes & Tools
● Sessions
○ Scrum Meeting (daily)
○ Backlog Refinement
grooming (1 or 2 per
Sprint)
○ Sprint planning 1 or 2
per Sprint)
○ Demo or Review (end
of Sprint)
○ Retrospective (end of
Sprint)
● Product Backlog
● Tools
○ Scrum Board
○ User Stories
○ Burn Down Chart
○ Timeboxing
○ Icebox
9. Team:
● The WHOLE scrum team is
onboard and committed
● Stakeholders have the
project as a priority—not
necessarily a top priority, but
available for answers
● Team is focused: don't get
many interruptions from
everyday business
● The team is fully skilled team
to match the project
● The team has the ability to
communicate frequently and
easily (daily stand ups, etc.)
Output:
● Something to show at the
end of the sprint
● The team gets a full sprint to
produce value without any
interruptions
● Anything after that may be
subject to change, this is
where a sprint really lives up
to its name
When to choose Scrum
Tools:
● A clear vision of the end
product
○ There needs to be
enough of a product
backlog for a few sprints
(2-3)
■ There can be
changes but the
team shouldn’t
stop working to
adapt to change
○ Scrum projects can
change direction as long
as the product backlog is
maintained and groomed
10. ● Sprint scope frequently changed due to “high priority”/ emergency situations
● Scope isn’t clear or is blocked
● Basic Scrum rules not fully enforce
● Releases start to be ad hoc
● No clear distinction between Project and Product
● Addressing maintenance and support work as main sprint goal
● Team dedication is erratic
When should Scrum turn to Kanban and Scrumban
11. KANBAN
Kanban is a visual signal that's used to trigger
an action. The word kanban is Japanese and
roughly translated means: “card you can see.”
Toyota introduced and refined the use of
kanban in a relay system to standardize the
flow of parts in their just-in-time (JIT) production
lines in the 1950s.
"Kanban promotes flow and reduced cycle-time
by limiting WIP and pulling value through in a
visible manner."
-Torbjörn Gyllebring
12. KanBan in a Nutshell
The project philosophy
● Kanban doesn’t prohibit
change, but it doesn’t
prescribe it either.
● Kanban encourages
making incremental
changes to avoid drastic
decrease in productivity
● Small course corrections
are also just easier than
altering the complete
process
● Vision of the end product
The Team
● Technical needs as per
requirement of the
project
Kanban recognizes that there
may be value in the existing
process, roles and
responsibilities
Take what is working and
preserve it.
Processes & Tools
● Sessions
○ Meeting (daily)
■ Often those that have
converted from Scrum
to Kanban,are inclined
to keep the daily
stand-up
● Product Backlog
○ Team to pull the tickets
● Tools
○ Kanban board
○ WIP limits
■ Limiting the amount of
WIP, at each step in the
process, prevents
overproduction and
reveals bottlenecks
dynamically so that you
can address them
before they get out of
hand.
13. When to choose Kanban
● Operation support
○ Running a production system as a whole,
● Maintenance work and support projects
● Continuous flow
○ No nee0d to stop to reassess just keep on going and deploying
● When the project requires the maximum flexibility and frequent
change of priorities and scope
○ When the goals are not clearly defined
○ Risk of scope creep
● Ad hoc releases required
● Team dedication is erratic
○ When team isn’t focused - responsibilities elsewhere.
● If management isn’t ‘into scrum’
○ Management isn’t giving the needed time and attention to the project
Focus
Courage
Openness
Respect
Commitment
14. SCRUMBAN
Mix of scrum and Kanban
Scrumban is a management framework
that emerges when teams employ Scrum
as their chosen way of working to
understand and continuously improve how
they work and use the Kanban Method as
a lens through which to view (kanban
board)
Scrum Kanban Scrumban+ =
● Scrumban comes into play to help teams with the transition from Scrum to Kanban. Can stay here a
while
●
● Scrum-ban is still unclear. Is it an improved Scrum or and improved Kanban
● Scrumban is not unique to the software development process
15. ScrumBan in a Nutshell
The project philosophy
Improvement on;
● Roles
● Work processes
● Better flows
● Flexibility
The Team
Like Scrum
● Cross functional
● Allowing for specialized
teams and functions
● Dedicated team
Processes & Tools
● Sessions (The Scrum)
● Stand up for daily check in
● Retro for team
improvement
● Review- for incremental
releases to demo to the
client
● Product Backlog
● Tools (The Ban)
○ Kanban board
○ Ad hoc release
○ Continuous flow
○ WIP limits
○ Pulling tickets
○ Grooming on demand
16. When to choose Scrumban
● Any Scrum with an unstable and/or moving vision
○ When the project requires the maximum flexibility and frequent change of priorities and scope
○ When the goals are not clearly defined
○ Constantly evolving product
○ Sprint planning isn’t happening
● If management isn’t ‘into scrum’
○ Management isn’t giving the needed time and attention to the project
● Any Kanban project that needs the structure of Scrum
○ Hard deadline
■ Still working to the objective
○ Team not focused
17. Extreme Programming (XP)
Extreme Programming (XP) is another agile development framework, focussed on improving software
quality and responsiveness to evolving client requirements. Extreme programming advocates frequent
releases in short development cycles in order to improve productivity and introduce checkpoints so that new
requirements can be accommodated.
Planning Game
Small Releases
Metaphor
Simple Design
Testing
Refactoring
Pair Programming
Integration
Collective Ownership
On–site Customer
40–Hour Work Week
Coding Standards
Other elements of extreme programming are: programming in pairs, code reviews, unit testing of all
codes, avoiding programming of features—until they are actually needed, a flat management structure,
simplicity, and clarity in code.
18. Software
Development
Extreme Programming XP (Prabhat )
● Extreme programming is
code first approach to
software delivery and
emphasizes on four basic
activities: coding, testing,
listening, designing.
● Extreme programming
brought testing at the
forefront of the delivery
process which helped with
evolution of core software
engineering.
● Practices like: automated
testing, refactoring,
continuous integration,
and test driven
development.
Planning
Design
Testing
Coding
Simple design
CRC cards
Spike solutions
prototypes
Refactoring
Pair Programming
Unit Test
Continuous
IntegrationRelease
Acceptance Testing
User stories values
acceptance test
criteria iteration plan
Project velocity
computed
19. Advantages & Disadvantages of Extreme Programming
Advantages
● Pair programming under XP helps in
writing better codes
● Increased team accountability
● Extreme Programming manages risks in a
better way
● Source code is always robust as simplicity
helps in faster development and less
defects
● Easy to accommodate changes
Disadvantages
Detailed planning is required right since the
inception of XP due to changing scope and
associated cost
● XP does not have a set measurement plan
or quality assurance for coding.
● Pair programming may lead to too much
duplication of codes and data.
● XP is more code centric than design which
may cause UI/UX issues in larger projects.
20. XP in a Nutshell
The project philosophy
● Code first
● Refactoring
● Simple designs
● Spike solutions
The Team
Team Size - 5 or less
● Tracker, Customer,
Programmer, Tester,
Coach
● Well-trained
● Specialized
● Co-located
Processes & Tools
● Pair programming
■ Planning game
● Release Plan
■ Iteration plan
● Project velocity
● Iteration - Usually 1 week
long
Practices
● Test driven development
● Continuous Integration
● Collective code ownership
21. When to use XP
When to use
● Have reached a certain level of maturity as usual tasks, defects
and smaller unrelated user stories
● Require maximum flexibility and frequent change of priorities
● Have multiple releases per week or per day
● Have many unscheduled releases
● Have less cross functional teams
Maturity
Flexibility
Unscheduled
Releases
Less cross
functional team
22. Lean Development
● Lean was adopted for the software industry in the
year 2000
● Later on lean was applied for startups in a book
“Lean Startups” by Eric Reis as a way of developing
new product and services in circumstances of
extreme uncertainty.
● A typical lean process: Learn-Measure-Build cycle,
performs quality analysis, and testing, frequently
connects with clients to understand the business
value and focuses on continuous improvement
● The continuous cycle leads to sustainability, smart
development, and success
Problem Solutions Key Metrics
Cost
Structure
Revenue
Stream
Channel
Advantage
23. Advantages and Disadvantages of LEAN
Advantages
● Complements existing practices.
● Focuses on project ROI.
● Eliminates all project waste.
● Cross-functional teams.
Disadvantages
● Does not specify technical practices.
● Requires constant gathering of metrics
which may be difficult for some
environments to accommodate.
● Theory of Constraints can be a complex
and difficult aspect to adopt.
24. Lean in a Nutshell
Key Principles
1. Eliminate Waste
2. Build Quality “in”
3. Create Knowledge
4. Defer Commitment
5. Deliver Fast
6. Respect People
7. Optimize the Whole
The Team
● Well-trained
● Specialized
● capable of
self-management
● Communicative
● Ability to make decisions
Processes and Tools
● Sessions
○ Daily Stand up
meetings
○ Operations Review
● Tools
○ Cumulative Flow
Diagrams
○ Visual Controls
○ Virtual Kanban
Systems
● Iterations
○ Small Batch sizes
○ Automation
25. Feature Driven Development
● Feature Driven Development is a pragmatic software process which is architecture
centric and focused to achieve the goal of client.
● Feature Driven Development was introduced in 1999 in a book named “Java
modeling in color with UML.”
● As the name suggests, features are an important aspect of FDD. These are the
primary source of requirements and primary input into the planning efforts in FDD.
● A feature is a small, client-valued function expressed in the form:
<action><result><object>.
26. Feature Driven Development
Develop
an Overall
Model
Build a
Features
List
Plan by
Feature
Design by
Feature
Build by
Feature
(more shape
than content)
An object model
+ notes
A list of features
grouped into sets
And subject areas
A development plan
Class owners
Feature set owners
A design package
(add more content to
the object model)
Completed
client-valued
function
Initial
Modeling
Model
Storming
27. Advantages & Disadvantages of Feature Driven Development
Advantages
● Supports multiple teams working in
parallel
● All aspects of a project tracked by feature
● Design by feature and build by feature
aspects are easy to understand and adopt
● Scales to large teams or projects well
Disadvantages
● Promotes individual code ownership as
opposed to shared ownership
● Iterations are not as well defined by the
process as other agile methodologies
● The model-centric aspects can have huge
impacts when working on existing systems
that have no models
28. FDD in a Nutshell
The project philosophy
● Multiple teams working
on the same project.
● Tracking through
features
● Model Centric Approach
The Team
● Project Manager
● Chief Architect
● Development Manager
● Chief Programmer
● Class Owner
● Domain Expert
Supporting roles
● Domain manager
● Release Manager
● Language Guru
● Build Engineer
● Toolsmith
● System Administrator
● Tester
● Deployer
● Technical Writer
Processes & Tools
● Develop an overall model
● Build a feature list
● Plan by feature
● Design by feature
● Build by feature
Practices
● Domain Object Modeling
● High level class diagrams
● Developing by feature
● Individual class ownership
● Reporting visibility of reports
29. Comparison table
Scrum Kanban Scrumban
Artifacts
simple board , product backlog,
sprint backlog, product increment,
burndown chart mapped on the process board mapped on the process board
Board Clean board for start of sprint same board continually used same board continually used
Ceremonies
daily scrum, sprint planning
sprint review
sprint retrospective on demand and optional Defined by the team
Teams & Roles SM, PO, Team, Small to Medium
Cross functional / specialized
teams with a possibility Agile
coach, Small to Medium
Cross functional / specialized
teams with a possibility Agile
coach, Small to Medium
Iterations Incremental Improvements
Constant Stream (not have
predefined)
Incremental Improvements OR
Constant Stream
Task Assignment Assigned to team Pulled by the team member Taken by each team member
prioritization
Part of backlog grooming, done
by PO
Out of the process. Backlog
should be prioritized
Out of the process. Backlog
should be prioritized
performance metrics Burn down chart
lead and cycle time and
cumulative flow
lead and cycle time and avg cycle
time
30. Comparison table
Extreme Programming FDD Lean Development
Artifacts
Release Plan, Metaphor, Iteration
plan
Features, high level class
diagrams
Cumulative Flow Diagram, Virtual
Kanban Board
Board Clean board for start of sprint Feature board Same board continually used
Ceremonies
daily meeting, planning game
on demand on demand and optional
Daily Stand up and operation
review
Teams & Roles
Tracker, Customer, Programmer
Coach
Project Manager, Chief Manager,
Architect, Class owner and so on
cross functional / specialized
Agile coach
Iterations Incremental Improvements Feature Development
Incremental Improvements OR
Constant Stream
Task Assignment Assigned by the customer Assigned to the team member Pulled by the team member
prioritization Done by Customer
Done by Project Manager or
Architect
Done based on the business
value
performance metrics Release plan
lead and cycle time and
cumulative flow
lead and cycle time and avg
cycle time
31. Which Methodology is right for you
We know about all the methodologies, advantages and
disadvantages now.
Now comes the question - which methodology is right for you?
Let’s use popular decision making framework CYNEFIN for it.
32. CYNEFIN
CYNEFIN describes the problem, situation, and systems—with the help of research—into
adaptive system theory, cognitive science, narrative patterns, and evolutionary psychology
Further it explores relationship between context, experience, and the person to propose
new approaches to communication, decision-making, policy making, and knowledge
management
● The term CYNEFIN was first coined by Welsh Scholar “Dave Snowden”
● George W. Bush administration used CYNEFIN for analysing policy and the impact of
religion in process
● CYNEFIN provides a typology of contexts that guides what kind of explanation or
solution may apply
● CYNEFIN has 5 domains: obvious, complicated, complex, chaotic, disorder
33. Chaotic
Lacking Constraint De–Coupled
act–sense–respond
Novel Practice
Obvious
Tightly Constrained No Degrees of Freedom
sense–categorise–respond
Best Practice
CYNEFIN
ComplicatedComplex
Enabling Constraints Loosely Coupled
probe–sense–respond
Emergent Practice
Governing Constraints Tightly Coupled
sense–analyse–respond
Good Practice
34. Obvious
Sense, Categorize, Respond
● No analysis required
● Cause and effect repeatable, known and predictable
● We use best practices for it and continue with the methodology we have been using for it
● Need to follow standard operating procedures
● Automation can also do the job
● Data provides answers
35. Complicated
Sense, Analyze, Respond
● Cause and effect separated over time and space
● We use our good practices
● We do predictive planning and expert analysis to reach the solution
● Data provides options, experts analyze and measure goodness
● Kanban or Scrumban or Lean fits well here depending upon the culture and suitability.
36. Probe-Sense-Respond
● Cause and effect seen in retrospect and do not repeat
● We use emergent practices for it
● We do sensemaking, stories and monitor coherence to find the solution
● Either Scrum or XP or FDD fits here well depending upon size of the project.
● We need to do pattern management and heuristics.
○ For example: more stories like this, less like this
Complex
37. Chaos
Act, Sense, Respond
● Cause and effect not usefully perceivable
● Act to bring stability and crises management
● Experience informs decision, action is required
● Noble practices are discovered, We can’t be assured with any methodology