Read how one PM used systematic problem-solving techniques to visualize, categorize and analyze problems and find underlying root causes—leading a project from red to green status in four weeks. This article suggests that a systematic approach to problem-solving can assist leaders in understanding problems and devising plans to resolve them promptly.
Conversations in Scrum
Oraib Nawash · Nov 28, 2023
5 hours ago Oraib Nawash replied 5 hours ago
Jill Blockson · Nov 27, 2023
12 hours ago Markus Kopko, PMP replied 12 hours ago
zeng zheng · Nov 16, 2023
Nov 20, 2023 Kimberly Whitby replied Nov 20, 2023
Sunil Prabhu · Oct 23, 2023
Oct 31, 2023 Nadia Shaheen replied Oct 31, 2023
Enrique Aparicio · Jul 16, 2019
Oct 24, 2023 Edward Calllaghan replied Oct 24, 2023
Maryam Imam · Oct 17, 2023
Oct 17, 2023 Mayte Mata-Sivera replied Oct 17, 2023
Alexandru Rosioru · May 25, 2023
Oct 13, 2023 Luis Branco replied Oct 13, 2023
Cassandra Medley · Aug 24, 2022
Sep 17, 2023 Sergio Luis Conte replied Sep 17, 2023
Anonymous · Sep 6, 2023
Sep 11, 2023 Keith Novak replied Sep 11, 2023
Koti Rupendra Ramarao · Aug 21, 2023
Aug 23, 2023 Abolfazl Yousefi Darestani replied Aug 23, 2023
As many organizations now incorporate Agile ways of working to manage projects, there are new roles to be filled. In Scrum, one of those roles is the Product Owner. Does your organization have an unclear role and responsibilities for your Product Owners? Are you a Product Owner who is looking for ways to be more effective and successful in your role? If so, this webinar is for you.
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
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.
Sprint planning is an important part of the agile process, but too often it’s treated as a perfunctory step to simply add stories to the upcoming sprint. Instead, teams should include goals, value and uncertainty in the discussion—and get much more out of it.
Question: I am going to head a team on a large, corporate project that will involve multiple teams. The problem is that we are not all going to be using the same methods of project management, and I am concerned about how we will be able to work together if we are not all following the same processes. Is it possible for various parts of the organization to work in different ways and still produce a good product?
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!