ProjectManager.com

NOVEMBER 22, 2021

A project management methodology is a set of principles, tools and techniques that are used to plan, execute and manage projects. Project management methodologies help project managers lead team members and manage work, while facilitating team collaboration. What Is a Project Management Methodology? Agile Methodology.

Technical Review 505

Technical Review Prince2 Manufacturing Lean 505

Rebel’s Guide to PM

MAY 17, 2022

As project managers, it’s important that we know how to best support our development teams (and vice versa), especially in Agile environments. Here is what we learned from an invaluable brainstorming session with our Tech Lead. In the Planning phase, the project manager also defines internal and external communications.

Technical Review 414

Technical Review Development Team Review Risk Management Agile 414

Rebel’s Guide to PM

MARCH 18, 2019

As project managers, it’s important that we know how to best support our development teams (and vice versa), especially in Agile environments. Here is what we learned from an invaluable brainstorming session with our Tech Lead. In the Planning phase, the project manager also defines internal and external communications.

Technical Review 399

Technical Review Development Team Review Agile Risk Management 399

Scrum.org

FEBRUARY 25, 2020

This time we take the perspective of the Development Team. Development Team – Why your Scrum Doesn’t work (2/3) (this post). The posts are based on my own experience when I practiced the roles of Development Team (member), Product Owner, and Scrum Master. Development Team.

Development Team Review 225

Development Team Review SCRUM Technical Review Closing 225

Scrum.org

JANUARY 10, 2021

Many organisations wrestle with the seeming incompatibility between agile and release management, and they struggle with release planning and predictable delivery. Professional Developers create working software. Release planning and predictable delivery. Updated to reflect the 2020 Scrum Guide! How can that possibly be!

Software Review 230

Software Review Technical Review Planning Manufacturing 230

Scrum.org

OCTOBER 12, 2020

Top 5 Things You Should Do During Sprint Planning . As per Scrum Guide – The Sprint Goal is an objective that will be met within the sprint by implementing the Product Backlog , and it guides the Development Team on why it is building the Increment. It reflects the maturity of the team and improving the quality of a product.

Planning 254

Planning Technical Review Development Team Review Software Review 254

Scrum.org

JUNE 17, 2019

TL;DR: Technical Debt & Scrum. If technical debt is the plague of our industry, why isn’t the Scrum Guide addressing the question of who is responsibly dealing with it? What Is Technical Debt? There is also a kind of technical debt that is passively created when the Scrum Team learns more about the problem it is trying to solve.

Technical Review 188

Technical Review SCRUM Software Review Development Team Review 188

Scrum.org

NOVEMBER 9, 2020

TL; DR: Scrum Sprint Planning Checklist. A Sprint Planning checklist? So, from my perspective, checklists are not an evil means of imposing standardized processes but a helpful tool for practitioners even if they are a Scrum Master using a Sprint Planning checklist. Scrum Sprint Planning Checklist – The Details.

Planning 225

Planning Technical Review Software Review SCRUM 225

Scrum.org

SEPTEMBER 14, 2020

Please find following the latest subset from the 47 Scrum Master interview questions to identify suitable candidates for the role of Scrum Master or agile coach: Product Backlog, refinement, and the Sprint Planning. Please note: Normally, the Product Owner would provide this information during Sprint Reviews or the refinement process.

SCRUM 240

SCRUM Planning Development Team Review Technical Review 240

Scrum.org

SEPTEMBER 23, 2019

The first article of this series will address the Scrum Master engagement with the Development Team. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team. Scrum Master Engagement with the Development Team. Agreed, this is tautological.

Development Team Review 166

Development Team Review SCRUM Software Review Technical Review 166

nTask

OCTOBER 21, 2021

Let’s take a look at all these project management applications for Linux in detail, and find out how they can help the managers and the team members in their workdays. One of the best applications that you can use as a project manager or a project development team member is nTask. Key Features. Configuration wizard.

Technical Review 179

Technical Review 2021 Software Review Software 179

ProjectManager.com

MARCH 31, 2020

As technology advanced, so did the workforce and how teams work. With broadband, mobile devices and software solutions, teams could be recruited anywhere and work remotely. Being able to clearly direct tasks and keep a channel open between manager and team is key to successful execution. It’s easy to neglect remote teams.

Software Review 424

Software Review Technical Review Monitoring Development Team Review 424

Scrum.org

MAY 17, 2021

That means that they need to have some level of knowledge of both the relevant business domain to help the Product Owner, as well as enough technical knowledge to help the Scrum Team. Are technical skills required to be a Scrum Master? At the time of writing there are more than 350k people with PSM I and 11k people with PSM II.

Technical Review 140

Technical Review SCRUM Development Team Review Certification 140

ProjectManager.com

MARCH 25, 2022

Agile project management is an iterative approach to delivering a project through short planning cycles called sprints. By using incremental steps towards completing a project, agile teams can easily adjust their project plan or product development plan to better meet their customer requirements. Agile Core Values.

Agile 312

Agile Software Review Technical Review Development Team Review 312

ProjectManager.com

SEPTEMBER 19, 2019

It must have over 100 positive reviews online, averaging 4 stars or greater. For example, a project manager can create a project plan in the Gantt view. Then, team members can work on their assigned tasks in simple task lists or boards. Commonly used in the software development industry, Trello is a popular collaboration tool.

2019 243

2019 Software Review Software Technical Review 243

Scrum.org

FEBRUARY 25, 2024

Scrum Anti-Patterns GPT’s Answer Organizational issues often lead to Scrum anti-patterns that can hinder the effectiveness and efficiency of Scrum Teams. Reassigning Team Members : Frequently moving team members between Scrum Teams disrupts the building of trust and undermines the stability and effectiveness of teams​​.

SCRUM 226

SCRUM ChatGPT Technical Review Development Team Review 226

Scrum.org

NOVEMBER 7, 2018

This is much easier to implement in the real world but also means it will be much harder for the team to self-organize because they have a team lead that isn't just focused on helping them improve via Scrum but is also their focal point for Scrum of Scrums, during PI Planning, etc. But we can't ignore the differences in lingo.

SCRUM 172

SCRUM Development Team Review Technical Review Cadence 172

Scrum.org

AUGUST 3, 2020

In the short term, communication and proactive planning is key. For a longer-term, more empowering state, consider cross-training, opening up permissions, organizational design changes, even hiring and team forming strategies. Scrum Master or Tech Manager. Got ugly dependencies? Let’s talk about getting to good.

Underperforming Technical Team 253

Underperforming Technical Team Technical Review Software Review Development Team Review 253

ProjectManager.com

MARCH 21, 2019

For example, a user story might be written like this, “As a project manager, I want to print out my Gantt chart, so I can review it regularly on my office wall.” ” The role would be project manager, the feature capability would be printing, and the benefit would be reviewing the chart on the wall. Overly Technical.

Technical Review 298

Technical Review 2005 Software Review Development Team Review 298

Scrum.org

SEPTEMBER 19, 2020

It's a key inspect and adapt opportunity for the Development Team, encouraging them check their progress towards the Sprint Goal and adjust their plan accordingly. It's also supposed to be an event for the Development Team and run by the Development Team but as we know in "the real world" it's not always implemented that way!

SCRUM 226

SCRUM Underperforming Technical Team Development Team Review Technical Review 226

Scrum.org

JULY 7, 2024

Teams must understand what is needed before they can deliver value. It's just a matter of whether it will be done in Sprint Planning, during the Sprint, or whether you will do it in advance of the Sprint as part of regular, planned refinement activities. Cons : Lacks collaborative input, may miss technical insights.

Technical Review 209

Technical Review Development Team Review 2024 Estimate 209

Kiron Bondale

SEPTEMBER 30, 2018

Some people may challenge this by stating that the SM needs capacity for daily standups, sprint planning, sprint reviews & retrospectives, but that should still leave them plenty of time to take on another role. When an SM is providing guidance to a team member, will that team member know which hat the SM is wearing?

SCRUM 212

SCRUM Technical Review Development Team Review Agile 212

Scrum.org

OCTOBER 12, 2020

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. Keeping technical debt at bay. A good Scrum Team pays attention to the preservation of an application’s technical health to ensure the Scrum Team is ready to actually pursue an opportunity in the market.

SCRUM 234

SCRUM Underperforming Technical Team Technical Review Software Review 234

Rebel’s Guide to PM

AUGUST 7, 2023

You could also interview experts, review lessons learned or innovative solutions from previous projects, research what the rest of your industry is doing or consult customers on what they’d like to see. Choose the creative approach that gets you a range of options to review. There are no silly ideas at this point!

Technical Review 332

Technical Review Consulting Monitoring Development Team Review 332

ProjectManager.com

NOVEMBER 5, 2019

Whenever there’s a project, there should be a plan. There are many different ways to plan a project, each with their own advantages and disadvantages. Choosing the right planning method ultimately depends on the complexity of your project and your organization. Phase 2: Building the Case Plan. Phase 3: Development.

Development Team Review 163

Development Team Review Process Underperforming Technical Team Technical Review 163

Scrum.org

APRIL 28, 2019

The Stacey model summarizes in the groups the complexity drivers of a problem: requirements to achieve, technology to use and people involved in the product development or use. . The Stacey Matrix of development complexity . How could people add complexity to the development of the product?

Technical Review 167

Technical Review SCRUM Software Review Defining 167

Scrum.org

MARCH 22, 2021

Join more than 100 peers from May 27-29, 2021 , for the Virtual Agile Camp Berlin 2021, a non-profit live virtual Barcamp using open space technology principles and practices. The team addressing unplanned priority bugs. Has the level of technical debt increased or decreased during the last Sprint?

SCRUM 235

SCRUM Underperforming Technical Team Development Team Review Technical Review 235

ProjectManager.com

JANUARY 2, 2020

It must have over 100 positive reviews online, averaging 4 stars or greater. For example, a project manager can create a project plan in the Gantt view. Then, team members can work on their assigned tasks in simple task lists or boards. Commonly used in the software development industry, Trello is a popular collaboration tool.

2020 196

2020 Software Review Software Technical Review 196

LiquidPlanner

SEPTEMBER 29, 2020

Sprint Planning: A sprint plan is a weekly plan created to meet specific goals that will contribute to the project’s overall completion. Sprint Review: At the end of the week, an assessment is conducted to evaluate how goals were met and how improvements may be implemented. When do You Need a Scrum Master?

SCRUM 193

SCRUM Development Team Review Technical Review Software Review 193

Scrum.org

MARCH 2, 2020

Where the organization needs to morph into a kind of ‘team of teams’ structure with a shared understanding of purpose and direction as well as the need to create value for the customers at heart, the reality of a legacy organization attempting to become agile is often very different. Sprint Planning Anti-patterns of Stakeholders.

SCRUM 243

SCRUM Development Team Review Underperforming Technical Team Technical Review 243

Scrum.org

JANUARY 11, 2023

The product owner must have knowledge about the customer needs as well as technical expertise to ensure that the right decisions are made regarding feature selection. They must have knowledge about customer needs and technical expertise to make feature selection decisions. A Day in the Life of a Product Owner.

Technical Review 209

Technical Review Software Review Agile SCRUM 209

Scrum.org

SEPTEMBER 13, 2021

Scrum Anti-Patterns: From Product Backlog to Sprint Review. I added new questions on Scrum anti-patterns, from the Product Backlog to the Sprint Planning to the Sprint Review, to provide more insight into the Scrum value creation process and the organization’s return on investment. Question 45: Scrum Master Anti-Patterns.

SCRUM 233

SCRUM Underperforming Technical Team Development Team Review 2020 233

ProjectManager.com

FEBRUARY 21, 2019

Either way, it’s a critical perspective for any organization that wants to plan for the future. Don’t get too technical, either, as that might limit the vision. Once you have a draft, review it. Once you’ve created a product vision, you’re able to plan how to realize it. Be specific; don’t generalize. The Elevator Test.

Technical Review 295

Technical Review Development Team Review Software Review Agile 295

Scrum.org

MARCH 31, 2019

Together they discover the Scrum Team can meet the purpose in other ways that are more effective and more efficient. . Instead of detailed technical documentation that is rarely referenced, hard to use, and difficult to maintain, a Development Team may choose to capture technical documentation in different ways.

Agile 170

Agile Software Review Technical Review Development Team Review 170

Scrum.org

JANUARY 9, 2023

Follow-up question : Why is it beneficial that the team adheres to the values and practices of Scrum? This can help improve the overall quality of the team's work and ensure that the team is meeting its goals. Question : Should a Scrum Master remove problems on behalf of the Scrum Team? Q 19: The Feasible Sprint Goal.

ChatGPT 227

ChatGPT SCRUM Underperforming Technical Team Technical Review 227

Scrum.org

APRIL 11, 2019

Firstly, there is often no clearly formulated vision, or a missing plan on how to achieve a vision. The PO’s are then unsure what needs to be developed. The other “fake PO’s” should be moved inside the development teams as subject matter experts so they can provide detailed requirements. Lack of product focus.

Underperforming Technical Team 180

Underperforming Technical Team SCRUM Development Team Review Software Review 180

Scrum.org

NOVEMBER 6, 2023

Technical prowess on the instrument does not necessarily lead to musicality. You can have amazing technique and still make terrible music if you don’t pay attention to the end goal. When I’m teaching Scrum or helping teams, I want everyone to remember how each piece of the Scrum Framework gets you closer to done, working software.

SCRUM 214

SCRUM Software Review Development Team Review Technical Review 214