This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
TL; DR: A Remote Sprint Review with a Distributed Team. This seventh article now looks into organizing a remote Sprint Review with a distributed team: How to practice the review with virtual Liberating Structures, including and giving a voice to team members, stakeholders, and customers.
Yet, in reality, some of the best leaders are quiet, introverted people who care deeply for their teams and stakeholders and quietly grind away toward a common goal. It can be learned and exercised on a small scale before being brought to bear on larger groups. This is another instance where having diversity on the team is helpful.
We had a look at common remote agile anti-patterns; we analyzed remote Retrospectives, Sprint Plannings as well as remote Sprint Reviews based on Liberating Structures. This eighth article now looks into supporting a distributed DevelopmentTeam organizing a remote Daily Scrum. Do you want to get this article in your inbox?
On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. When a weak DevelopmentTeam meets a commanding Product Owner, focusing on shipping new features, the team may end up as a feature factory, churning out new code while neglecting the technical foundation.
Product discovery using the Design Thinking, Lean Startup, or Lean UX frameworks help, but in any case, a good Scrum Master will want the Scrum Team to be a part of this process (whether by participating in user interviews or running experiments). There is greater respect among stakeholders for the product delivery teams.
Reassigning Team Members : Frequently moving team members between Scrum Teams disrupts the building of trust and undermines the stability and effectiveness of teams. In the absence of this feedback, teams may engage in gold-plating under the assumption that they are adding value.
Lean/Agile Leadership. Both SAFe and Scrum/Nexus emphasize the need for a different style of leadership - leaders who serve, have a growth mindset, lead by example, live and breath Lean/Agile principles and practices, and strive for relentless improvement. . The Nexus reviews, retrospects, plans, and refines together every Sprint.
As a Scrum Master, you develop and help others develop strategies to become more successful with Scrum. How is the DevelopmentTeam going to collaborate to achieve the Sprint Goal? How does management interact with Scrum Teams? You decide to use Mad Tea , a Liberating Structures in Development.
The POPM Training is a two-day course that focuses on the role of the SAFe® Product Owner and how it fits into Agile teams. SAFe® for Lean Enterprises is a knowledge base of proven, integrated principles, practices, and competencies for achieving business agility using Lean, Agile, and DevOps. SAFe® Lean Portfolio.
Agile is all about staying lean and adapting to user feedback, right? The essential elements of a lean, mean one-pager PRD. However, Agile teams are taking an increasingly adaptive approach to project planning , by constantly adding requirements to their backlog and prioritizing them as they come up. Jump to a section.
Designing something is typically a consensus-gathering and problem-solving exercise. Approaches like lean, kanban and agile work well in these uncertain, high-change environments. The developmentteam wants interesting work using new technology and skills to further their craft.
They aim to instil lean concepts of respect for people, minimization of waste, and value delivery. Iterative development of small batches of work, with frequent reviews, provides better insights into progress and issues than sequential, large-batch development.
Keep reading to find out more about this essential role in your company’s software developmentteam. A Scrum Master is a facilitator who helps a Scrum team to self-organize, collaborate, and continuously improve. Facilitating daily stand-up meetings with the team. Providing feedback to the team. ICP-ACC) Training.
Value Stream Mapping (VSM) is a lean management technique for process improvement that has its roots in the manufacturing sector. So, let’s get started: Background and Historical Perspective Value Stream Mapping (VSM) emerged as a fundamental component of Lean Manufacturing, a methodology pioneered by Toyota in the 20th century.
Transforming organizations to become Lean and Agile while maintaining high levels of performance within its teams requires a strong focus on people. After all, these high-performing teams are the ones that deliver change and growth. My role model for personal development and lifelong learning is my grandfather Gustav.
Review and update your Agile roadmap every few months. With the right Agile planning process in place, you can use your team’s wisdom and insight to think big without losing the iterative and feedback-driven qualities that make Agile so magical. Developmentteams care about products, features, and user behaviors.
I was showing their developmentteams how to automate functional tests using Cucumber. During a workshop for one of the teams, I learned they did not write or maintain application code. As they were working through the hands-on exercises, their lead Business Analyst asked, “Can Cucumber read Excel files?”
For most developmentteams and startups, ‘becoming Agile’ starts and ends with how you build software. But a full Agile transformation isn’t just about the development process you use — it’s a way to bring creativity, innovation, and lean operations to every aspect of your business. This is ok.
They aim to instil lean concepts of respect for people, minimization of waste, and value delivery. Iterative development of small batches of work, with frequent reviews, provides better insights into progress and issues than sequential, large-batch development.
A critical part of every program increment planning is to define the complete PI planning exercise, how it works and clearly stating the goals and end-objectives of doing the entire event in the first place. Embarking on this feedback activity helps flag and resolve all potential issues before the final management review takes place.
You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. Is it something we need to review? Or, the worst case is because some software developer said so. Fletcher Hearns: And then, project adherence to best practices.
They do daily stand-ups, they do reviews and retrospectives. And lean manufacturing frontline workers can always safely pull the cord if they start to see problems, everything stops, the issue gets solved. Within that context, we have to create safety for the developmentteams to tell the truth. You can’t have it.
You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. They aren’t prince to experts, they don’t have a Lean Six Sigma Black Belt. And I promise, I won’t make this a typing exercise. Kyle: Okay.
And now you’re trying to sell them that quitting this plan will turn out to be mutually beneficial—if they trust the product development entity’s ambition to develop into an agile, learning, customer-centric organization. There are plenty of opportunities for stakeholders to interact responsibly with a Scrum Team.
models: The first experiment compares the Scrum Guide 2017 to the Scrum Guide 2020 The second experiment is designing a Retrospective exercise The third experiment is to help a new Scrum team to design a Definition of Done. The Product Owner and Scrum Master are now considered equal members of the Scrum Team.
Reviewing code by eyeballing it to ensure compliance with coding standards. Preparing test data to exercise applications prior to deployment. An unattended CI/CD pipeline has to satisfy the needs of all stakeholders without requiring a halt for manual review and approval. Provisioning and configuring environments.
We organize all of the trending information in your field so you don't have to. Join 100,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content