Scrum masters and project managers can form a formidable leadership team on agile initiatives. But how does that relationship and scrum master’s role evolve in a hybrid environment? For one, more attention to coaching and less to process.
The daily standup is a key Agile practice. Since the latest Scrum Guide release, it has changed and become less rigid than before, no longer relying on the key three questions. In addition, for teams running Kanban, the daily standup can take on a different form.
Have you ever wondered why innovative organizational leaders and high-performing developers, product designers, UX specialists, etc. - who are otherwise excellent at what they do - are slow and hesitant to adopt Agile methodologies? Agile transformation is a hot topic right now, but many organizations rush the implementation process without pausing to assess and address foundational issues. The truth is, new hires or new Agile teams aren’t entirely convinced that Agile methodologies can support their expertise and simplify their day-to-day tasks. They perceive Agile transformation as “just another thing” their company is trying and are reluctant to commit. In this workshop, I’ll present a road map that will help agile practitioners and executives interested in agile transformation identify the root cause of resistance of new Agile teams and new hires. We’ll also look at the challenges Agile evangelists such as Scrum Masters, Agile Coaches, and POs face in implementing these methodologies. The goal is to get all Agile stakeholders aligned with a company’s or a product’s vision and reframe how Agile is seen and used by everyone involved. After this interactive presentation, Agile specialists, executives, and product owners will know exactly how to facilitate Agile transformations with a culture-first approach, supported by coaching, mentorship, and the right kind of accountability (avoiding micromanagement). The result? Teams who truly believe in the potential of Agile methodologies and continue to incrementally incorporate them in their work without resistance, thus accelerating their learning curve.
Save Time With Tools And Templates
This template can be used to estimate costs for a project based on Scrum iterations/sprints. This tool assumes basic knowledge of agile/Scrum. The template is divided into three spreadsheets: Overview (detailed explanation of the template and usage), Estimator (calculations required for obtaining project cost estimates) and Data (look up data used in the estimator worksheet).
Scrum has been at the forefront of a revolution in how software is developed and deployed. Who is using it? How? And why? In this exclusive 48-page report from ProjectsAtWork, Scrum Alliance and ProjectManagement.com, 500 professionals share their answers.
This 19-slide deck is a companion piece to the Agile Distributed Teams research report from ProjectsAtWork. It is designed to help you leverage the report's key findings and recommendations to achieve the benefits of working with distributed agile teams in your organization.
The purpose of the Scrum of Scrums is to synchronize projects that are interdependent upon one another and to discuss any roadblocks, impacts and mitigation strategies. Use this simple PowerPoint deck to track project progress and roadblocks.
Learn From Others
Prototyping, scrum, SAFE, kanban...it's easy to get confused these days. Here we walk through some of the main project methodologies used for IT projects today and give a little history of each—with some recommendations for when each methodology might be most appropriate.
Question: Even as we begin to emerge from the challenges of the past year, it is becoming obvious that things will never go back to exactly how they were in the past. My company wants me to use more agile approaches, along with our past predictive ones, to make us more flexible. But while I agree in concept, I’m not too sure how this would work in practice. Any suggestions?
Does the Daily Scrum help your team grow, or do they waste time? Here is some insight on the importance of holding Daily Scrums—and how you can actually use them as a tool for team cohesion.
In agile product development, we try to work on fewer things and stick with them until we finish. Rapid priority shifts are expensive and demoralizing. But that’s not always clear on the go-to-market side, so we need stories like the Hungry Man Parable to build better understanding.
Question: We are starting a project that is part hardware and part software driven. The organization has asked me if we want to use a traditional approach or a more flexible version like agile. It seems to me that the production line would benefit more from one and the IT team might do better with another. What do I recommend to management about what our team wants to adopt to move forward?
Scope creep can plague projects where timelines are established at the start, or budgets and resources are fixed. However, it should not be a problem for projects operating with agile principles. Rather than resisting change, an agile team welcomes it, and figures out how to adapt to it. Here's how.
We received so many questions during our Ask the Experts: Agile for the Rest of Us webinar that we didn’t have time to answer them all, so the presenters continue the conversation here!
If we stubbornly insist on running projects “by the book,” we are going to miss opportunities. In that spirit, here are six ways to develop your hybrid approach to project management.
Scrum masters are critical to the success of agile projects, but as agile skills and experience in an organization grow, does the role need to evolve to remain effective?
After you've assembled a cross-functional innovation team and aligned around a goal, it's time to start using metrics and data to track the most important things, supported by a scorecard that everyone can see. This will help establish a rapid rhythm and generate positive velocity on your innovation journey.
Ask a Question