Page: 1 2 3 4 5 6 7 8 9 10 11......26 next>
If you're losing the attention of your team during meetings, it may be time to look at other ways to increase engagement. Let’s go through three different styles that morning meetings can take—and see which one may be right for your team.
Question: We are an organization that has both manufacturing type teams and those who do more software-oriented things. Management really wants us to do things that are more similar in the way we manage projects. Since what we do doesn’t really lend itself to a single approach to the work we need to complete, how can we set up something that works for both parts of the organization?
Does an agile team need a project manager? Should a scrum master be bossy? A practitioner in a software development project makes some observations as he adapts to a new way of working.
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.
Holding a retrospective during a crisis is a completely different process than it is during less stressful times. As a PM, you should be aware of the appropriate methods to use when this happens. A practitioner from Ukraine shares her experiences.
Are you a stickler for "agile rules" when using agile project management? Don't be! That's just one of the lessons this practitioner has learned over the years through hands-on experience succeeding—and failing—while working on agile efforts.
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.
Page: 1 2 3 4 5 6 7 8 9 10 11......26 next>
|
"Man prefers to believe what he prefers to be true." - Francis Bacon |
