The IIL Blog

DECEMBER 11, 2024

The bad news is that this complicates the decision on which to choose. Clear Deadlines and Roles Each team member’s deadlines are listed clearly next to their tasks and they can see how those deadlines impact others’ deadlines [3]. It also makes it easier for the team to understand their tasks [4].

Artificial Inteligence 78

Artificial Inteligence Leadership Software Review 2024 78

Scrum.org

OCTOBER 12, 2020

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. As somebody hiring for a Scrum Team, you need to determine for yourself what works for your organization — which is a process, not a destination. Generally, insisting that the team achieve specific KPI, e.

SCRUM 234

SCRUM Underperforming Technical Team Technical Review Software Review 234

Leading Answers

JUNE 22, 2022

This is part one in a series on leading agile teams from the Beyond Agile book. We will examine what leadership entails and how it applies to agile teams. We can create backlogs and release plans all we like, but until there is a motivated team with a shared vision of the end goal, it is like trying to push a rope—ineffective.

Leadership 193

Leadership Underperforming Technical Team Development Team Review Lean 193

Scrum.org

MARCH 11, 2023

Why do we deliver poor quality? More things to think about come from Marty Cagan's “Inspired” book. The tool: Product Opportunity Assessment (POA): What problem will this solve? Why do we build unnecessary products? Why are we most often too late? Why are most products more expensive than expected? Do we try to analyze more?

Underperforming Technical Team 195

Underperforming Technical Team Development Team Review Risk Management Risk 195

Scrum.org

JULY 21, 2020

Regularly, we find articles from developers detailing why ‘Agile’ in general and Scrum’s nature, in particular, deserve our collective disdain. These rigid methodologies inevitably turn developers into mindless cogs in a corporate machinery—churning out more and more code—while ignoring the true potential of these knowledge workers.

Software Review 224

Software Review Underperforming Technical Team SCRUM Engineering 224

Scrum.org

NOVEMBER 28, 2020

What is important about Scrum is that it is a framework, and Scrum Teams need to define their process, practices, and tools within the framework. If you’ve taken a Professional Scrum course with me or read my book , you know my thoughts on best practices. Having a team within a team was a bit confusing. Absolutely!

2020 222

2020 SCRUM Underperforming Technical Team Software Review 222

Digite

MAY 15, 2018

In the most recent post in Steve Porter’s series, Yuval Yuret presents Scrum in a manner that is intended to educate Kanban teams. It also encourages everyone to review/adopt the values (in Scrum language) that can help software development teams succeed in building software. Disclaimer. You should go read it now.

Development Team Review 93

Development Team Review Software Review Underperforming Technical Team SCRUM 93

Scrum.org

JULY 29, 2019

In my role as an Agile coach and Scrum trainer, I get the chance to talk to a lot of Scrum Masters and teams. When I ask them about what their team is measuring, the most common answers I hear are velocity, story points, and burn-down charts. Team health? I often failed to help developers understand its true purpose.

Technical Review 180

Technical Review Underperforming Technical Team Development Team Review Software Review 180

Scrum.org

FEBRUARY 22, 2022

In both instances I was happily working as a developer and some form of team lead, when over a short period of time my role in the organization changed significantly and I faced serious challenges in learning completely new ways of working. . I couldn’t review all the code or be in on every discussion and decision.

Software Review 209

Software Review Underperforming Technical Team Technical Review Development Team Review 209

Scrum.org

NOVEMBER 18, 2020

Well, they are not new, lets take a trip down memory lane to the year 2009 and the book “The Toyota Kata” by Mike Rother. . See the Professional Scrum Product Owner book for more details. Development teams and stakeholders can “see” how they connect. Try aligning your Product Goals with quarterly business reviews.

2009 234

2009 Underperforming Technical Team Cadence SCRUM 234

Scrum.org

MARCH 19, 2023

Get notified when the Scrum Anti-Patterns Guide book is available ! This allows me to have a more up-to-date understanding of the world, including newer events and developments. While the core data sources might be similar, such as books, articles, and websites, the data sets themselves would not be identical across these models.

ChatGPT 172

ChatGPT SCRUM Technical Review 2020 172

Scrum.org

MARCH 4, 2019

Newly trained Agilists typically are assigned to join an existing project team by means of an experiment. Most people in the team are unhappy and try to switch projects, but not the Scrum Master. Following initial experiments, organizations get started with a real Scrum team. Pre-Scrum waterfall . Starting with Early Scrum.

SCRUM 154

SCRUM Software Review Development Team Review Underperforming Technical Team 154

Leading Answers

DECEMBER 21, 2017

My first opportunity to create and run a large agile team did not start well. Having had good successes with small to medium sized agile teams I was keen to unleash the benefits on a bigger scale. A clean-sheet development opportunity with a smart team and engaged business group – what could go wrong?

Governance 121

Governance Government Process Underperforming Technical Team 121

Scoro

NOVEMBER 25, 2024

Teams and clients aren’t aligned on the pricing model When you and your clients are conflicted over payment terms (fixed vs. hourly), costs can quickly spiral out of control. Document these terms in your proposal and review them with your client, working together to come up with a final quote that works for both sides.

Project Cost 52

Project Cost Technical Review Software Review Underperforming Technical Team 52

Scrum.org

JULY 1, 2019

Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment.”. By consequence, teams will ultimately abandon Scrum in such environments. . Ask yourself how successful your Scrum in reaching those two objectives.

SCRUM 161

SCRUM Underperforming Technical Team Development Team Review Controlling 161

Scrum.org

MARCH 4, 2019

Newly trained Agilists typically are assigned to join an existing project team by means of an experiment. Most people in the team are unhappy and try to switch projects, but not the Scrum Master. Following initial experiments, organizations get started with a real Scrum team. Pre-Scrum Waterfall . Starting with Early Scrum.

SCRUM 25

SCRUM Software Review Development Team Review Underperforming Technical Team 25

Planio

NOVEMBER 11, 2020

Have you ever had one of those bad dreams where you keep making the same mistake over and over again? Now, what if that dream became your team’s reality? If you feel like your team keeps making the same mistakes over and over, they probably are. Agile teams made retrospectives popular, but they work for any team.

Underperforming Technical Team 135

Underperforming Technical Team Development Team Review SCRUM Agile 135

Leading Answers

MAY 8, 2022

Some teams continue trying agile; others revert back to how they were. The practices we see agile teams undertake are just the visible components of a much larger ecosystem. All it achieves is to frustrate people and give agile a bad name. Let's review some popular techniques often seen on Scrum teams.

Agile 109

Agile Underperforming Technical Team Technical Review Software Review 109

Wrike

JULY 23, 2024

Workflows run your business processes, ensure consistency and compliance, and stop your team from skipping crucial steps. If you’re reading this, we’re going to assume you already know what workflows are and what they can do for your team. This is where workflow optimization comes in.

Underperforming Technical Team 36

Underperforming Technical Team Software Review Development Team Review Monitoring 36

Leading Agile

NOVEMBER 13, 2018

In discussing the delivery capacity of a software development team, we can say “velocity” and everyone knows we mean the amount of work the team can complete, on average, in a given time interval , and we don’t mean, literally, va=v+v02. Seems like it should; wouldn’t that mean the team is improving?

Software Review 113

Software Review Underperforming Technical Team Software Developers Software Development 113

Wrike

APRIL 10, 2025

Monitor the gap between the ideal line (projected progress) and the actual effort line (real progress) to assess if youre on schedule. This is usually marked as days or weeks, but some teams prefer to measure in Agile story points , which estimates how much effort it takes to complete a user story. How do I read a burndown chart?

Underperforming Technical Team 36

Underperforming Technical Team Estimate SCRUM Risk Management 36

Leading Agile

NOVEMBER 2, 2020

The best way to achieve early ROI with Agile is to create a delivery engine where the teams at the execution level are aligned with the business strategy. They will say things like, “I’ma a hint Jeff Sutherland wrote a book.” And we can start, you know, obviously getting revenue to fund further development.

Agile 118

Agile Development Team Review Underperforming Technical Team Consulting 118

The IIL Blog

SEPTEMBER 6, 2023

The History of Agile Project Management Agile project management emerged in the software development industry in the late 1990s and early 2000s. In 1991 the book Rapid Application Development was published and an approach of the same name, RAD, was born. Agile projects are iterative and have regular feedback loops.

Agile 88

Agile Underperforming Technical Team Software Review Development Team Review 88

Wrike

JUNE 29, 2023

Imagine you’re writing a book and you’ve just finished your first draft. The code review process is like the editing phase in writing a book. The code review process is like the editing phase in writing a book. You give it to someone else to read — this person is like the code reviewer.

Software Review 36

Software Review Technical Review Development Team Review Process 36

Leading Answers

DECEMBER 21, 2017

My first opportunity to create and run a large agile team did not start well. Having had good successes with small to medium sized agile teams I was keen to unleash the benefits on a bigger scale. A clean-sheet development opportunity with a smart team and engaged business group – what could go wrong?

Governance 60

Governance Government Process Underperforming Technical Team 60

International Institute for Learning

SEPTEMBER 20, 2022

According to a common and general definition, Team Management can be seen as the ability of an individual (manager) or of an organization to lead a group of people to accomplishing a task or common goal. Good management of a team means to do the best by and for the employees. By Luigi Morsa.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52

Wrike

FEBRUARY 21, 2017

You’re managing a large project team full of diverse working habits, communication styles, and preferences. From night owls and early birds to planners and procrastinators, you feel like your team is one big melting pot of a dozen different approaches. Who’s Who on a Project Team? But on the other hand? says Harrin.

Underperforming Technical Team 36

Underperforming Technical Team Development Team Review Leadership Construction 36

Herding Cats

JUNE 12, 2018

This is simply good process development and management. This, of course, is simply poor process improvement and a fallacy since without the root cause the symptom cannot be fixed and will return. We assess physical percent complete at close business every single day, with the update of the TO DO field in Rally at the Task level.

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

Workamajig

FEBRUARY 28, 2018

Here are the key collaboration habits from this article at a glance: Successful teams are purpose-driven, have a balanced mix of personalities, and communicate frequently. Involving team members in assigning project roles and setting goals can improve their performance. The ‘why’ defines the purpose of the team and its work.

Underperforming Technical Team 70

Underperforming Technical Team Technical Review Energy Leadership 70

Planio

FEBRUARY 13, 2018

When teams are working on the same project (or ones that influence each other), working in a cloud environment, where changes are immediately saved and synced, is essential. Along these same lines, if an app crashes and a company has poor IT support, the failure could easily hinder the progress of multiple employees who rely on the system.

Underperforming Technical Team 60

Underperforming Technical Team Technical Review Development Team Review Software Review 60

Leading Agile

NOVEMBER 3, 2020

To accelerate ROI, we must reliably put the right combination of working tested product in front of customers so that it can drive revenue, self-fund further product development, and create opportunities to get critical feedback. They will say things like, “I’m a hint Jeff Sutherland wrote a book.” And life is good.

Agile 69

Agile Development Team Review Underperforming Technical Team Consulting 69

Wrike

JULY 1, 2024

Done well, strategic planning will help you focus on your long-term business development, instead of just reacting to changes and challenges in the market. Try Wrike for free Book a demo Essential elements of a strategic plan Let’s start with the common elements of a strategic plan and the things you can consider as you lay one out.

Planning 36

Planning Underperforming Technical Team Development Team Review Technical Review 36

Herding Cats

JUNE 12, 2018

This is simply good process development and business management. This, of course, is simply poor process improvement and a fallacy, since without the root cause the symptom cannot be fixed and will return. The notion of waterfall development on slide 9 as actually prohibited in our domain. Have you done a Root Cause Analysis?

Underperforming Technical Team 28

Underperforming Technical Team Software Engineering Estimate Development Team Review 28

Herding Cats

AUGUST 27, 2017

The original post, while likely well meaning, coming from direct experience, focuses on ME the developer. And like many posts and tweets about estimating, it's made from this point of view, not the business point view, not from the point of view of those paying the developer. This Value is developed during the Product Planning session.

Estimate 46

Estimate Software Review Underperforming Technical Team Technical Review 46

MPUG

MAY 6, 2021

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. Individual contributor team, lead section, lead project manager, program manager, director of engineering. What does the team care about? What are their concerns?

Performance Measurement 52

Performance Measurement Underperforming Technical Team Governance Government 52

MPUG

DECEMBER 10, 2021

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. Melanie: Okay, Melanie here with Team MPUG. Also, as the President and Founder of Advisicon, Tim has written over 38 books on PM methodologies and technologies.

Software Review 52

Software Review Technical Review Underperforming Technical Team Engineering 52

Scrum.org

MARCH 22, 2021

Your Scrum team is consistently failing to meet commitments, and its velocity is volatile. How would you address this issue with the team? If a Scrum Team is exhibiting a volatile velocity, consistently failing to meet their forecasts, it suggests that velocity is being used as the prevalent metric for measuring that team’s progress.

SCRUM 235

SCRUM Underperforming Technical Team Development Team Review Technical Review 235