The Empowering Agile Teams Presentation has been presented at numerous Agile Conferences and has been VERY well received. Many teams get frustrated due to the lack of understanding of what they are expected to deliver vs what has been perceived. Gone are the days of opacity. Teams are better equipped to handle the day to day workload and are less fearful of commitment in an environment where healthy team relationships are valued.
Facilitation Foundations - A Guide to Effective Agile MeetingsAgileDad
Facilitation Foundations is a presentation that has been given at multiple Agile Conferences. The focus of the presentation is improving the quality and effectiveness of Agile Meetings.
Many who have downloaded this deck have made it a standard for assisting organizations who are struggling with spending too much time and money on Agile Meetings.
Identifying, Managing, & Eliminating Technical Debt is the key to successfully getting your business on track. Gone are the days where we could write endless checks that we did not have the people to cover. We need to work harder to make the debt known and address the debt up close and personal before it gets out of hand.
The purpose here is to educate the Agile work place about what technical debt is, learn how to eliminate it, and how to avoid ever running into it again.
The document provides information about a rapid release planning session and workshop led by V. Lee Henson. It discusses Henson's background and qualifications, which include founding an agile training company in 2007 and certifications in scrum, project management, lean, kanban and other frameworks. The document then covers topics that will be addressed in the workshop, including defining roles for release planning, writing effective user stories, estimating story size and prioritizing work.
Talk delivered by Craig Smith at YOW! West 2015 in Perth on 26 May 2015.
With 73% of the world using Scrum as their predominant Agile method, this session will open up your eyes to the many other Agile and edgy Agile methods and movements in the world today For many, Agile is a toolbox of potential methods, practices and techniques, and like any good toolbox it is often more about using the right tool for the problem that will result in meaningful results.Take a rapid journey into the world of methods like Mikado, Nonban, Vanguard and movements like Holocracy,Drive and Stoos where we will uncover 40 methods and movements in 40 minutes to help strengthen your toolbox.
Mature agile teams essential patterns v4 - half day workshopdrewz lin
This document outlines 21 patterns of mature agile teams. Some key patterns include: having an emergent architecture that evolves with each sprint; achieving different levels of "done-ness" for work, stories, and releases; practicing aggressive refactoring; investing in continuous integration; and ensuring organizational leadership is aligned with agile principles. The document provides examples and discussion topics for each pattern to help teams assess their own maturity and identify areas for improvement.
This document provides an overview of an Agile product design and project management presentation. The presentation covers traditional waterfall project management, the transition to more iterative approaches like Lean and Agile. It defines Agile and Scrum methodologies, provides examples of real-world Agile applications, and concludes with an activity where attendees work in teams to practice Agile techniques by developing a menu.
The document provides an agenda and overview for an introductory presentation on Agile and Scrum frameworks. It discusses Scrum roles, ceremonies, values and principles. The presentation covers the Scrum framework, roles, planning, estimation, team engagement and simulations. It also discusses Agile and Lean roots and contrasts Scrum with traditional waterfall approaches.
The Empowering Agile Teams Presentation has been presented at numerous Agile Conferences and has been VERY well received. Many teams get frustrated due to the lack of understanding of what they are expected to deliver vs what has been perceived. Gone are the days of opacity. Teams are better equipped to handle the day to day workload and are less fearful of commitment in an environment where healthy team relationships are valued.
Facilitation Foundations - A Guide to Effective Agile MeetingsAgileDad
Facilitation Foundations is a presentation that has been given at multiple Agile Conferences. The focus of the presentation is improving the quality and effectiveness of Agile Meetings.
Many who have downloaded this deck have made it a standard for assisting organizations who are struggling with spending too much time and money on Agile Meetings.
Identifying, Managing, & Eliminating Technical Debt is the key to successfully getting your business on track. Gone are the days where we could write endless checks that we did not have the people to cover. We need to work harder to make the debt known and address the debt up close and personal before it gets out of hand.
The purpose here is to educate the Agile work place about what technical debt is, learn how to eliminate it, and how to avoid ever running into it again.
The document provides information about a rapid release planning session and workshop led by V. Lee Henson. It discusses Henson's background and qualifications, which include founding an agile training company in 2007 and certifications in scrum, project management, lean, kanban and other frameworks. The document then covers topics that will be addressed in the workshop, including defining roles for release planning, writing effective user stories, estimating story size and prioritizing work.
Talk delivered by Craig Smith at YOW! West 2015 in Perth on 26 May 2015.
With 73% of the world using Scrum as their predominant Agile method, this session will open up your eyes to the many other Agile and edgy Agile methods and movements in the world today For many, Agile is a toolbox of potential methods, practices and techniques, and like any good toolbox it is often more about using the right tool for the problem that will result in meaningful results.Take a rapid journey into the world of methods like Mikado, Nonban, Vanguard and movements like Holocracy,Drive and Stoos where we will uncover 40 methods and movements in 40 minutes to help strengthen your toolbox.
Mature agile teams essential patterns v4 - half day workshopdrewz lin
This document outlines 21 patterns of mature agile teams. Some key patterns include: having an emergent architecture that evolves with each sprint; achieving different levels of "done-ness" for work, stories, and releases; practicing aggressive refactoring; investing in continuous integration; and ensuring organizational leadership is aligned with agile principles. The document provides examples and discussion topics for each pattern to help teams assess their own maturity and identify areas for improvement.
This document provides an overview of an Agile product design and project management presentation. The presentation covers traditional waterfall project management, the transition to more iterative approaches like Lean and Agile. It defines Agile and Scrum methodologies, provides examples of real-world Agile applications, and concludes with an activity where attendees work in teams to practice Agile techniques by developing a menu.
The document provides an agenda and overview for an introductory presentation on Agile and Scrum frameworks. It discusses Scrum roles, ceremonies, values and principles. The presentation covers the Scrum framework, roles, planning, estimation, team engagement and simulations. It also discusses Agile and Lean roots and contrasts Scrum with traditional waterfall approaches.
Talk delivered by Craig Smith at YOW! 2015 in Melbourne, Brisbane and Sydney on 4-10 December 2015.
With 73% of the world using Scrum as their predominant Agile method, this session will open up your eyes to the many other Agile and edgy Agile methods and movements in the world today For many, Agile is a toolbox of potential methods, practices and techniques, and like any good toolbox it is often more about using the right tool for the problem that will result in meaningful results.Take a rapid journey into the world of methods like Mikado, Nonban, Vanguard and movements like Holocracy,Drive and Stoos where we will uncover 40 methods and movements in 40 minutes to help strengthen your toolbox.
Refactoring the Organization Design (LESS2010)Ken Power
These are the presentation slides from a presentation I gave at the Lean Enterprise Software and Systems Conference 2010 (LESS 2010, http://less2010.leanssc.org/). The presentation is based around the paper I submitted that is published in the proceedings.
From the paper abstract:
Every organization has a design. As an organization grows, that design evolves. A decision to embrace agile and lean methods can expose weaknesses in the design. The concept of refactoring as applied to software design helps to improve the overall structure of the product or system. Principles of refactoring can also be applied to organization design. As with software design, the design of our organization can benefit from deliberate improvement efforts, but those efforts must have a purpose, and must serve the broad community of stakeholders that affect, or are affected by, the organization. Refactoring to agile and lean organizations demands that we have a shared vision of what the refactoring needs to achieve, and that we optimize the organization around the people doing the work.
Talk delivered by Craig Smith at itSMF NT meeting in Darwin, Australia on 22 March 2018.
With 73% of the world using Scrum as their predominant Agile method, which has a direct impact on service management, this session will open up your eyes to the many other Agile and edgy Agile methods and movements in the world today. For many, Agile is a toolbox of potential methods, practices and techniques, and like any good toolbox it is often more about using the right tool for the problem that will result in meaningful results. You may also be surprised about how many methods have a direct relation or reliance on service management as well as the wider organisational structure and culture. So let’s take a rapid journey into the world of methods like Mikado, Nonban, Vanguard and movements like Holocracy, Drive and Stoos where we will uncover 40 methods and movements in 40 minutes to help strengthen your understanding and toolbox.
The document provides an agenda and overview of an introductory training on Agile and Scrum frameworks. It discusses key concepts like the Agile Manifesto, Scrum values and roles, and the differences between Scrum and traditional Waterfall methodologies. It also covers topics like product vision, role engagement, planning, estimation, and Scrum simulations.
"Lean software development: discovering waste" by Mary PoppendieckOperae Partners
The document discusses lean principles for software development. It notes that standard lean tools designed for operations may not be appropriate for application development. Lean principles for development focus on building the right thing, building it right, and delivering fast through techniques like designing based on customer needs, reducing waste from extra features and handoffs, embedding quality through testing, and minimizing technical debt.
The Essential Product Owner - Partnering with the teamCprime
Bob Galen shares real-world stories where he’s seen “effectively partnered” teams and Product Owners truly deliver balanced value for their business stakeholders. In this session he’ll show you how story mapping and release planning can truly set the stage for effective team workflow—establishing a “Big Picture” for everyone to shoot for. How establishing shared goals, both at the iteration and release levels, truly cements the partnership between team and Product Owner. And finally, how setting a tempo of regular, focused backlog grooming sessions establishes a mechanism for the team and Product Owner to explore well-nuanced and high value backlogs.
This is a presentation I gave at the Central Indiana MPUG September 2012 meeting.
Abstract:
There are many commonly held myths about agile. Two of these myths are that agile projects don’t do any planning and that you can’t do agile on a fixed date project. In this presentation we will disprove these two myths by exploring just how agile planning is accomplished and how you can not only use agile on fixed date projects but also improve your accuracy and consistency in hitting those dates with agile.
This is my latest presentation on "Scrum managing through complexity" given at Luxembourg Sacred Heart University Executive MBA Class (Jan. 17th 2012).
This is a part of the Operational Excellence Module.
This document discusses how Agile principles and practices can support ITIL frameworks. It advocates that development adopt Agile methods fully through automation, customer involvement, and focus on quality. It also stresses the importance of operations participating in development and allowing frequent changes. Adopting these approaches can improve service quality, reduce risks, and foster collaboration between teams. The document provides advice such as implementing process changes incrementally and ensuring both process owners and managers are involved.
This document provides an overview of Acceptance Test Driven Development (ATDD) for building web applications. It begins with an introduction to the author and their company Futurice. It then defines ATDD as expressing functional requirements as concrete examples or expectations prior to development. The document discusses benefits of ATDD such as establishing a shared understanding of requirements, early regression detection, and producing executable documentation. It also notes potential challenges of ATDD including difficulty, lack of automation, and initial overhead. Finally, it provides steps for formulating test cases and demonstrates an example using a stopwatch application.
ALN-Bengaluru - Agile Management - Driving Leadership & Complexity of …Ravi Kumar
This document discusses agile management and the role of managers. It addresses the challenges of applying traditional management approaches to agile software development processes, which are characterized as complex adaptive systems. The document outlines several agile principles and manifestos focused on customer satisfaction, transparency, and self-organizing teams. It also examines different views of management and measurements, and argues future management approaches must focus on people, continuous improvement, and adapting to change rather than only efficiency.
Presentation delivered by Craig Smith at Fusion in Sydney, Australia in September 2012.
When XP and Scrum were devised over 10 years ago, they were created to improve the delivery of software development projects. As many enterprises have matured in the Agile adoption, many of the business users on IT projects are now attempting to use Agile approaches on their own non-IT projects.
In this session we will cover using Agile in a non-IT environment and demonstrate how the original XP practices map extremely well over to business processes. And how those in SD can help your business counterparts.
Expectations from IT Team
Project Methodology - Why it is as important as the Technology for your Product
Gaps in Recent Graduates
How to bridge these gaps?
This is a talk on experiences using agile techniques to manage projects in a number of businesses.
For more details see http://www.coclarity.com/blog/2009/11/speaking-at-leroei-event-on-agile-management/
This presentation debunks many of the mythologies surrounding the philosohpies and methodologies of Lean. Starting with the fundamental premise that value is defined by the customer, the presentation reviews the principles of Lean in the context of the 21st century economy, and what this means to you and your organization. Connect your organization’s day-to-day activities with Lean concepts and “learn to see” in ways that fundantally transform how you lead, manage, and work.
This document provides an overview of leading agile product development. It discusses moving from traditional to agile approaches, continuously improving by eliminating waste, creating flow in the product development process, optimizing backlogs and planning releases and roadmaps. The key aspects covered are adopting best practices for agile, lean, and complexity-aware development as well as exploring one's own views on agile practices.
1) The document provides an overview of CollabNet's agile transformation strategy and services. It discusses CollabNet's background and industry recognition. It also outlines common challenges faced by clients before adopting agile and typical results achieved after engaging CollabNet for agile transformations.
2) The document covers CollabNet's approach to agile adoption, which includes identifying pilot projects, establishing communities of practice, formalizing processes, and scaling agile enterprise-wide. It also discusses key phases in the pathway to becoming an agile enterprise.
3) Case studies are presented on agile transformations achieved with clients such as Deutsche Post, DHL, Amdocs, Nokia, and Intel that resulted in
The document discusses agile engineering and federated application lifecycle management (ALM). It defines agile practices like Scrum, Lean, XP and Kanban. It also discusses challenges with agility like testing overhead and keeping up with emerging technologies. Federated ALM is defined as integrating metadata, workflows and processes across development stages with customizable application development and integration flows.
Talk delivered by Craig Smith at YOW! 2015 in Melbourne, Brisbane and Sydney on 4-10 December 2015.
With 73% of the world using Scrum as their predominant Agile method, this session will open up your eyes to the many other Agile and edgy Agile methods and movements in the world today For many, Agile is a toolbox of potential methods, practices and techniques, and like any good toolbox it is often more about using the right tool for the problem that will result in meaningful results.Take a rapid journey into the world of methods like Mikado, Nonban, Vanguard and movements like Holocracy,Drive and Stoos where we will uncover 40 methods and movements in 40 minutes to help strengthen your toolbox.
Refactoring the Organization Design (LESS2010)Ken Power
These are the presentation slides from a presentation I gave at the Lean Enterprise Software and Systems Conference 2010 (LESS 2010, http://less2010.leanssc.org/). The presentation is based around the paper I submitted that is published in the proceedings.
From the paper abstract:
Every organization has a design. As an organization grows, that design evolves. A decision to embrace agile and lean methods can expose weaknesses in the design. The concept of refactoring as applied to software design helps to improve the overall structure of the product or system. Principles of refactoring can also be applied to organization design. As with software design, the design of our organization can benefit from deliberate improvement efforts, but those efforts must have a purpose, and must serve the broad community of stakeholders that affect, or are affected by, the organization. Refactoring to agile and lean organizations demands that we have a shared vision of what the refactoring needs to achieve, and that we optimize the organization around the people doing the work.
Talk delivered by Craig Smith at itSMF NT meeting in Darwin, Australia on 22 March 2018.
With 73% of the world using Scrum as their predominant Agile method, which has a direct impact on service management, this session will open up your eyes to the many other Agile and edgy Agile methods and movements in the world today. For many, Agile is a toolbox of potential methods, practices and techniques, and like any good toolbox it is often more about using the right tool for the problem that will result in meaningful results. You may also be surprised about how many methods have a direct relation or reliance on service management as well as the wider organisational structure and culture. So let’s take a rapid journey into the world of methods like Mikado, Nonban, Vanguard and movements like Holocracy, Drive and Stoos where we will uncover 40 methods and movements in 40 minutes to help strengthen your understanding and toolbox.
The document provides an agenda and overview of an introductory training on Agile and Scrum frameworks. It discusses key concepts like the Agile Manifesto, Scrum values and roles, and the differences between Scrum and traditional Waterfall methodologies. It also covers topics like product vision, role engagement, planning, estimation, and Scrum simulations.
"Lean software development: discovering waste" by Mary PoppendieckOperae Partners
The document discusses lean principles for software development. It notes that standard lean tools designed for operations may not be appropriate for application development. Lean principles for development focus on building the right thing, building it right, and delivering fast through techniques like designing based on customer needs, reducing waste from extra features and handoffs, embedding quality through testing, and minimizing technical debt.
The Essential Product Owner - Partnering with the teamCprime
Bob Galen shares real-world stories where he’s seen “effectively partnered” teams and Product Owners truly deliver balanced value for their business stakeholders. In this session he’ll show you how story mapping and release planning can truly set the stage for effective team workflow—establishing a “Big Picture” for everyone to shoot for. How establishing shared goals, both at the iteration and release levels, truly cements the partnership between team and Product Owner. And finally, how setting a tempo of regular, focused backlog grooming sessions establishes a mechanism for the team and Product Owner to explore well-nuanced and high value backlogs.
This is a presentation I gave at the Central Indiana MPUG September 2012 meeting.
Abstract:
There are many commonly held myths about agile. Two of these myths are that agile projects don’t do any planning and that you can’t do agile on a fixed date project. In this presentation we will disprove these two myths by exploring just how agile planning is accomplished and how you can not only use agile on fixed date projects but also improve your accuracy and consistency in hitting those dates with agile.
This is my latest presentation on "Scrum managing through complexity" given at Luxembourg Sacred Heart University Executive MBA Class (Jan. 17th 2012).
This is a part of the Operational Excellence Module.
This document discusses how Agile principles and practices can support ITIL frameworks. It advocates that development adopt Agile methods fully through automation, customer involvement, and focus on quality. It also stresses the importance of operations participating in development and allowing frequent changes. Adopting these approaches can improve service quality, reduce risks, and foster collaboration between teams. The document provides advice such as implementing process changes incrementally and ensuring both process owners and managers are involved.
This document provides an overview of Acceptance Test Driven Development (ATDD) for building web applications. It begins with an introduction to the author and their company Futurice. It then defines ATDD as expressing functional requirements as concrete examples or expectations prior to development. The document discusses benefits of ATDD such as establishing a shared understanding of requirements, early regression detection, and producing executable documentation. It also notes potential challenges of ATDD including difficulty, lack of automation, and initial overhead. Finally, it provides steps for formulating test cases and demonstrates an example using a stopwatch application.
ALN-Bengaluru - Agile Management - Driving Leadership & Complexity of …Ravi Kumar
This document discusses agile management and the role of managers. It addresses the challenges of applying traditional management approaches to agile software development processes, which are characterized as complex adaptive systems. The document outlines several agile principles and manifestos focused on customer satisfaction, transparency, and self-organizing teams. It also examines different views of management and measurements, and argues future management approaches must focus on people, continuous improvement, and adapting to change rather than only efficiency.
Presentation delivered by Craig Smith at Fusion in Sydney, Australia in September 2012.
When XP and Scrum were devised over 10 years ago, they were created to improve the delivery of software development projects. As many enterprises have matured in the Agile adoption, many of the business users on IT projects are now attempting to use Agile approaches on their own non-IT projects.
In this session we will cover using Agile in a non-IT environment and demonstrate how the original XP practices map extremely well over to business processes. And how those in SD can help your business counterparts.
Expectations from IT Team
Project Methodology - Why it is as important as the Technology for your Product
Gaps in Recent Graduates
How to bridge these gaps?
This is a talk on experiences using agile techniques to manage projects in a number of businesses.
For more details see http://www.coclarity.com/blog/2009/11/speaking-at-leroei-event-on-agile-management/
This presentation debunks many of the mythologies surrounding the philosohpies and methodologies of Lean. Starting with the fundamental premise that value is defined by the customer, the presentation reviews the principles of Lean in the context of the 21st century economy, and what this means to you and your organization. Connect your organization’s day-to-day activities with Lean concepts and “learn to see” in ways that fundantally transform how you lead, manage, and work.
This document provides an overview of leading agile product development. It discusses moving from traditional to agile approaches, continuously improving by eliminating waste, creating flow in the product development process, optimizing backlogs and planning releases and roadmaps. The key aspects covered are adopting best practices for agile, lean, and complexity-aware development as well as exploring one's own views on agile practices.
1) The document provides an overview of CollabNet's agile transformation strategy and services. It discusses CollabNet's background and industry recognition. It also outlines common challenges faced by clients before adopting agile and typical results achieved after engaging CollabNet for agile transformations.
2) The document covers CollabNet's approach to agile adoption, which includes identifying pilot projects, establishing communities of practice, formalizing processes, and scaling agile enterprise-wide. It also discusses key phases in the pathway to becoming an agile enterprise.
3) Case studies are presented on agile transformations achieved with clients such as Deutsche Post, DHL, Amdocs, Nokia, and Intel that resulted in
The document discusses agile engineering and federated application lifecycle management (ALM). It defines agile practices like Scrum, Lean, XP and Kanban. It also discusses challenges with agility like testing overhead and keeping up with emerging technologies. Federated ALM is defined as integrating metadata, workflows and processes across development stages with customizable application development and integration flows.
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.
Making Scrum Stick Inside Heavy Regulated Industries (2012) Laszlo Szalvay
Laszlo Szalvay is a VP at CollabNet who oversees their global Scrum business. He has extensive experience helping organizations adopt and scale agile practices. Prior to CollabNet, he co-founded Danube, a leader in Scrum tools and training, which was later acquired by CollabNet. He is a recognized expert in implementing distributed agile environments and addressing cultural challenges.
The document provides an overview of traditional waterfall project management models and their weaknesses. It then introduces agile methodologies and the agile manifesto. A large portion of the document focuses on describing the Scrum agile framework, including roles, artifacts, meetings, and how Scrum works. It discusses advantages like improved visibility and ability to cope with changes, as well as potential disadvantages like requiring experienced teams and user involvement.
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.
The Secret Sauce for Innovation (shortform) Laszlo Szalvay
The document summarizes Laszlo Szalvay's presentation on innovation and agility at Agile Brazil 2012. It discusses how organizations can become more innovative through adopting an agile mindset. The presentation covers 5 steps for organizations: 1) become a learning organization, 2) focus on employee retention, 3) implement community architecture, 4) have a clear executive vision, and 5) use user stories to articulate requirements. The goal is to help organizations innovate through increased agility.
The document provides an introduction to lean and agile software development. It discusses common problems with traditional software development approaches and introduces the Agile Manifesto and its 12 principles. It then describes several popular agile methodologies like Scrum, Extreme Programming (XP), and Lean Software Development. Finally, it outlines some standard practices for agile software development projects, including iteration planning, key meetings, roles, requirements management, tools, development, and testing.
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.
This document discusses why DBAs should care about Scrum. It provides an overview of Scrum, describing it as an agile framework that utilizes self-directed cross-functional teams, short sprints, and transparency. It notes that Scrum can help reveal issues in an organization and improve outcomes compared to traditional sequential development approaches. The document encourages DBAs to stay up-to-date on new methodologies like Scrum in order to provide more value and help teams be more successful.
The Role of Project Professionals Creating Agile Organisations - PMI UK Agile...Andrea Darabos
What is the role of project professionals in creating more agile organisations? How do traditional PMI roles - project manager, program manager, PMO manager, portfolio manager - change as a company adopts more agile ways of working? What is servant leadership? How can we build and maintain self-organising teams? How can an organisation move from project based agile delivery to a more lean approach, based on continuous flow of value via value streams? How does project and portfolio governance change in an agile evolution? We are going to answer these questions based on the personal experience of the author working with agile teams and program offices in 8 countries.
Overview of Agile for Business AnalystsSally Elatta
This seminar was presented to the IIBA Omaha group. My goal was to provide a quick overview of Agile and then dive into the role and skills needed for a BA on an Agile team. Let me know if you would like me to present this or a similar topic at your organization. sally@agiletransformation.com
Overview of agile values
This presentation shows some core concepts that make agile software development different.
This will help your team familiar with agile concepts and start boosting your team performance.
Integrating agiledevsixsigmabp mandcm-presenteddrewz lin
This document discusses integrating agile software development with six sigma, business process management, and configuration management. It provides an agenda that will define these enterprise disciplines, discuss how practitioners of each discipline can interact with agile development, and provide exercises to think about how to integrate the disciplines. The presentation is given by Jason Tice, Vice President of Asynchrony, and provides background on large-scale agile transformations at the enterprise level.
From Waterfall to Agile - from predictive to adaptive methodsBjörn Jónsson
In this introduction into Agile methods, the background and environment of Software Development is discussed. Results of the 1995 Chaos report are mentioned, as well as interests in adaptive "lightweight" methods. Agile methods are explained in general and Scrum method taken as a concrete sample.
The document discusses several Agile methodologies including Scrum, Extreme Programming (XP), Dynamic Systems Development Method (DSDM), Feature Driven Development (FDD), and Crystal methodologies. It provides details on their core principles, practices, roles, and processes. An example project is also described to illustrate the successful use of XP in developing image processing software within time and with almost no bugs.
Communicating agile project status to executive managersAgileDad
The document discusses communicating agile project status to executive managers. It provides tips for establishing trust between management and agile teams. It also outlines appropriate roles for executives, managers, and teams in an agile environment. The document recommends focusing reporting on working software demonstrations and metrics like burn down charts and velocity, rather than intensive intra-sprint reporting.
This document discusses adopting open source software in enterprises. It outlines that open source is being adopted for reasons such as price, agility, control and quality. Both top-down, driven by CTOs and bottom-up, driven by engineers are discussed as drivers of adoption. Successful adoption requires selecting strategic beachhead projects, building communities of expertise, and varying levels of involvement with open source communities depending on the maturity of the project.
The document compares the roles of a ScrumMaster and a Project Manager. It notes that while a Project Manager is responsible for planning, executing, and closing projects using a predictive methodology like waterfall, a ScrumMaster acts as a facilitator and servant leader within an agile team. Specifically, the ScrumMaster helps remove impediments, safeguards the Scrum process, fosters communication, and serves the team, whereas the Project Manager focuses more on schedules, budgets, resources and requirements. The document provides more details on the responsibilities and skills of a ScrumMaster compared to a traditional Project Manager.
Similar to Introduction_to_Scrum_Agile_Values (20)
Organizational Design Scaling in Retail [Agile, Lean]Laszlo Szalvay
Massage Envy Franchising, LLC (MEF, Franchisor) lacks an effective goto market for new multi-unit Massage Envy Franchisees. These are my thoughts on that topic.
Proposed Title Fear and Loathing in Agility: Long Live the Accounting Departm...Laszlo Szalvay
"A dead ScrumMaster is a useless ScrumMaster,” echo the votary of Ken Schwaber (Co-Founder of Scrum) folklore. In this session hosted by Pat Reed (Agile Alliance Board Member) and Laszlo Szalvay (Executive at SolutionsIQ) we will explore how and why the accounting department needs to be your biggest champion as you embark on your next agile transformation. Pat and Laszlo will walk through concrete steps and real world examples of how capitalization works with Scrum and what you need to tell the accountants so they don’t shoot you.
So don’t end up a dead ScrumMaster.
Agile 2013: Pat Reed and I discussing Scrum and Compliance Laszlo Szalvay
To become a mainstream methodology, Agile had to overcome many potential obstacles. The first was geography…One of today’s most daunting obstacles is compliance, often bringing heavyweight documentation, required procedures that are very waterfall-ish, complex approval work flows, and complicated approval processes begins Compliance Is A Hurdle, Not A Barrier, To Agile a Forrester Research paper published in July 2011.
This presentation will walk attendees through the problem of why organizations trying to manage a software development life cycle or PMO in a heavily regulated industry are fraught with challenges (e.g. externally mandated documentation levels, limiting the requirements and scope of the Product Owner, morale of employees). The presenters will discuss the fact that many of the external compliance standards (FASB, MAS, FSOC) are vague, and worse yet not written with the software development team in mind. In fact one of the risks is the interpretation of policy or external compliance standard remains on the business or with an executive (through personal / fiduciary guarantees). For example, authors of US Federal legislation (e.g. Dodd Frank Act) do not specifically consider software development when writing laws and are often ignorant to the downstream effects of said legislation for a development team based in Russia or India. When asked for clarifications the FSOC does not know enough about software development to provide clear and concise answers and the amount of documentation in the said legislation can be (a) in the thousands of pages and (b) within living documents.
Creating Environments for Innovation to Flourish discusses key principles for fostering innovation. It outlines a 5 step guide: [1] become a learning organization by solving problems; [2] retain intrinsically motivated employees through slack and bottom-up ownership; [3] implement community architecture using open source principles; [4] have a clear executive vision through techniques like vision sessions; and [5] use user stories to articulate requirements. The document emphasizes that innovation emerges from diverse, self-organizing teams when given autonomy, motivation, and opportunities to learn and improve.
This document outlines an agenda for an executive team presentation focusing on developing features for the second half of 2013. It includes several group exercises:
1. Listing potential new features on sticky notes and organizing them into themes.
2. Individual and group dot voting to rank features by perceived customer benefit.
3. Relative sizing and ROI calculation to estimate effort and organizational prioritize the backlog of features.
The presentation aims to have an interactive and hands-on discussion of real product needs and develop an agreed upon prioritized backlog for upcoming development.
Scrum and Compliance for Scrum Gathering Vegas (2013)Laszlo Szalvay
This document discusses making Scrum work in regulated industries. It addresses challenges with compliance requirements and how they can be a hurdle to Agile practices. The document presents quotes from government officials about their experiences using Scrum. It then outlines an agenda to discuss market trends, how teams want to work versus requirements, and potential organizational patterns to address compliance in an Agile way. Case studies are presented and an exercise is described for attendees to build their own organizational pattern.
The document discusses making agile work in regulated industries. It notes that compliance requirements can bring heavyweight documentation and complex approval processes that are challenging for agile. However, some government organizations like the FBI have found success adopting agile practices. The document also provides examples of developer preferences and organizational patterns that can help balance compliance needs with agile values.
This is my current work and thinking on how to do Scrum within heavily regulated industries like healthcare, government, and finance. For more information join my community at http://scrumandcompliance.com/
The Secret Sauce for Innovation (longform) Laszlo Szalvay
Laszlo Szalvay is a business leader, entrepreneur and industry expert of implementing Scrum and Agile-based practices for global IT organizations. Though his experience, he has identified five practical steps that every organization should adopt and make part of their DNA. At Agile Brazil 2012 Szalvay will outline the process of combining Agile concepts with a new approach to innovation that organizations can use to create surprising breakthroughs in new product creation and development. Using a wide range of real-world examples, interactive exercises and an engaging discussion style, Szalvay will provide every participant with useful insights that can be immediately applied to re-invigorate and nourish product innovation.
Agile 2012 Conference briefing deck for Analyst and Press Laszlo Szalvay
This is the CollabNet briefing deck that was used at the Agile 2012 tradeshow. It features updates from our thought leaders books, our Products (ScrumWorks Pro 7.0 release) and our new messaging around Enterprise Cloud Development (ECD).
Enterprise Cloud Development and Agile Transformation Strategy - China 2012 Laszlo Szalvay
This is a seminar I gave throughout China the week of Oct 29th 2012. It covers the topics of Agile Software Development (Scrum, Lean, XP) and the new framework of Enterprise Cloud Development that CollabNet has been socializing. Please contact me for similar private talks at your company.
This document discusses strategic vision and Scrum. It notes that strategic vision is important for knowing organizational initiatives, defending product direction, fostering collaboration, and delighting users. It provides techniques for creating and fostering vision, including executive vision sessions, story mapping, walking skeletons, and epic budgeting. The document also provides background on CollabNet, a company that provides tools for agile development and source code management.
Making Scrum Work Inside Small Businesses Laszlo Szalvay
This document discusses how entrepreneurs can benefit from using Scrum. It recommends that entrepreneurs incorporate a culture of learning and questioning, use both qualitative and quantitative metrics like cash on hand and number of happy customers and employees, and do Scrum at the organizational level across functions like marketing, sales, and executives. Adopting these agile practices can help entrepreneurs build learning organizations that continuously solve problems and adapt.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdfflufftailshop
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
CollabNet was founded in 1999 with the goal of creating a better way to build software. At that time Brian Behlendorf’s strategy (our founder) was focused on “how to connect talented developers regardless of where everyone was physically located”. In today’s terminology, CollabNet wanted to enable “geographically distributed development teams” and provide them a way to all work as ONE TEAM. Finding that CVS, one of the most popular version control systems available at the time, had various issues, CollabNet decided to commission development of a brand new version control system called Subversion. In 2000, CollabNet founded the Subversion open source project and recruited its first developers. Since then, we have continued to sponsor and foster the Subversion project. This includes: hosting the physical project servers in our data center, guaranteeing uptime, providing technical support, and working with the press and analyst community to increase exposure and drive adoption. Perhaps most importantly, we maintain a team of full-time Subversion committers who are dedicated to contributing code and driving a product roadmap. As most of you know, we recently announced version 1.7 that finally addressed Merge Tracking, this was a big request from the community. For companies who have now standardized on Subversion and are then looking to have Technical Support (like having insurance for SVN – someone to call if there is major issue) we offer 3 levels of Support which you can find on our website. We also provide migrations services and web based training. From our openCollabNet site you can download our CollabNet Subversion that EXTENDS SVN giving you additional functionality like Certified binaries and IDE support. Along with our dedication to Subversion we also provide the CollabNet TeamForge platform which will cover shortly.
01/16/13
01/16/13
You are working with known technology Requirements are complete and unchanging The process is highly repeatable 01/16/13
A team of 100 is really no team at all. It’s a collection of 100 individuals.
In software being agile means different things to different people, but usually we all share a few basic characteristics. For inspiration lets check out our manifesto 01/16/13
A team of 100 is really no team at all. It’s a collection of 100 individuals.
If you have incompetent people, terrible managers, an awful product and no customers, Scrum will not fix that. Then again, neither will any other method. Scrum will make these things visible so the organization can work on those problems. Scrum assumes that teams are made of technically competent professionals who know how to make decisions within their sphere of expertise. Scrum will provide a simple framework to help successful systems, efforts, and people shine, while revealing things (and people) that aren’t working towards success. (This can be very painful when there are PEOPLE who are contributing to failure and it becomes visible…)
Detailed up-front planning and defined processes are replaced by adaptive inspect and adapt cycles. Pay attention Validate (Inspect/test) all artifacts Adapt to the realities you see Team is self-managing and organizes itself around goals given constraints. Team self-organization is the key difference between Scrum and other brands of agile.
Product Owner Defines the features of the product, decides on release date and content Is responsible for the profitability of the product (ROI) Constantly prioritizes the Product Backlog Can change features and priority every sprint Accepts or rejects work results ScrumMaster Helps resolve team and organizational based impediments Ensures that the team is fully functional and productive Enables close cooperation across all roles and functions and removes barriers Shields the team from external interferences Ensures that the process is followed. Invites to daily Scrum, iteration, review and planning meetings Team (Development Team and Available Customers) Cross-functional, 7 ± 2 members Negotiates the iteration goal and specifies tasks Has the right to do everything within the boundaries of the project guidelines to reach the iteration goal Organizes itself and its work Demos work results to the Product Owner and other Stakeholders 01/16/13
Daily Stand-up (Daily Scrum) The team understands its status every day in order to do a daily “inspect and adapt” cycle. Ask three questions (what did you do today, what did you do yesterday, what’s impeding you to get done what it is you need to get done. Sprint Planning The Product Owner and team agree on the subset of the Product Backlog to work on this sprint. This subset is the Sprint Backlog. Sprint Review The Team shows their Product to their Product Owner and other Stakeholders. The purpose is to “show off” and get buyoff and feedback. Sprint Retrospective The team (or Scrum Team) analyzes its own process and modifies it as necessary Backlog Grooming Comb through the backlog and work on the building of stories, Def. Of Done of stories, etc etc
Lets study the basics and some metrics and advanced topics too… 01/16/13