Velociteach

FEBRUARY 1, 2023

Projects using well-understood solutions and technologies require less rigor. Problem complexity, technical complexity, compliance requirements, and the cost of change factor into this decision. Projects where the problem and technical complexity are low, and the cost of change is high may favor a predictive methodology.

Planning 52

Planning Technical Review Governance Government 52

Leading Answers

MARCH 7, 2019

Consultants will say,  “Oh, it depends…”  and start a lengthy (aka expensive) conversation. When our projects undertake defined, repeatable work using technologies and approaches our organizations have experience in, then uncertainty and change rates are typically low and manageable.

Software Review 101

Software Review Technical Review Risk Management Software Developers 101

Planio

AUGUST 9, 2021

What is the best project scheduling software to use? Monday.com: Best for non-technical teams. Ask each person to help estimate their workload, uncover dependencies, and set deadlines for due dates. Consult those goals (as well as any risks you’ve identified) to get a feel for the project’s outline.

Software Review 78

Software Review Technical Review Estimate Agile 78

Leading Agile

MAY 3, 2023

And you know, we get into clients like that and our consultants get faced with these things all the time where you live in this kind of this weird dichotomy of I know these things must be true to be successful, but the organization doesn’t seem to want to change them. Are we doing reviews? Is there a burn down chart?

Agile 62

Agile Technical Review Governance Government 62

Leading Agile

APRIL 20, 2023

How many people are consultants or team members that feel like managers don’t know how to empower their teams? We can make our bottom box bigger with some technologies and some expertise, some experience. And teams have a cadence where they’re operating with intent but within constraints. A lot of those things.

Agile 62

Agile Underperforming Technical Team Cadence SCRUM 62

Leading Agile

JANUARY 21, 2021

And what we are is we’re a consultancy that’s focused on doing Agile Transformation specifically. So it’s like the ability to form teams, the ability to create clear backlogs the ability to get to a working tested increment of software at the end of every sprint. So we started LeadingAgile about 10 years ago.

Sustainability 93

Sustainability Agile SCRUM Technical Review 93

Leading Agile

MARCH 31, 2020

– I was working in my office down in technology Parkway. You get super clear backlogs, you find out what the real cadences you’ve finished work that you start. And it’s not always get better the technology get better the processes, it’s get better producing the outcome. And BPR was about the technology.

Agile 63

Agile Technical Review SCRUM Engineering 63

Leading Agile

AUGUST 19, 2020

So the first lens or the first set of foundational things that we’re going to talk about when it comes to predictability is the idea of the three things, teams, backlogs, working tested software. They deliver it, they review it with the product owner, product owner says yes, and then they get to claim the points, right?

Agile 87

Agile SCRUM Governance Government 87

Digite

FEBRUARY 13, 2018

Dave is a Principal Consultant at Depth Consulting Ltd, and Program Director of the KCP Program at the Lean Kanban University. In this article, he outlines the similarities of the two as WIP Limiting, Pull-based systems – with cadences and a focus on learning – while also explaining their differences. Increments.

Cadence 94

Cadence SCRUM Lean Underperforming Technical Team 94

Planio

AUGUST 1, 2022

For most development teams and startups, ‘becoming Agile’ starts and ends with how you build software. According to research published in Harvard Business Review , nearly 90% of companies struggle to complete Agile transformations — even after successful pilot projects. But unfortunately, few companies can pull it off.

Agile 78

Agile Technical Review Leadership Infrastructure 78

Planio

MARCH 13, 2023

This leaves you at risk of becoming one of the 54% of projects fail that fail due to poor KPI tracking. On the other hand, if you’re working at a small tech startup, your report might focus more on costs and timelines. Review who receives your updates every so often and add new people as you go. Target it to those who need it.

Underperforming Technical Team 78

Underperforming Technical Team Software Review Technical Review Risk Management 78

Wrike

FEBRUARY 20, 2023

It is especially useful in software development and enterprise product management as these teams tackle projects and programs on extended timelines with continuous improvements, upgrades, and iterations released and delivered to customers over time. What is the Scaled Agile Framework?

Agile 36

Agile Development Team Review Lean Underperforming Technical Team 36

Leading Agile

OCTOBER 3, 2023

And so we ended up with a lot of folks doing standups and sprint planning and story cards and sticky notes and burndown charts and reviews and retrospectives. And so I was thinking about Scrum and so I just lifted this off of Mike Cone’s website and it’s attributed, so I hope he doesn’t mind too much mountain good software.

Governance 62

Governance Government SCRUM Agile 62

Leading Agile

MARCH 17, 2021

Do they own the technology or do they have dependencies with tons of teams around them? But what I would suggest that it’s only a concern to the extent that we’re a profitable company, that we can put out software when we say we’re gonna put out software or put out product, when we say we’re gonna put out product.

2021 62

2021 Agile Underperforming Technical Team SCRUM 62

Leading Agile

FEBRUARY 11, 2019

It’s time now to move forward to the next level of proficiency in software delivery; what we might call “post-Agile.” Today, some of the same principles seem to present impediments or unnecessary challenges for many teams and organizations. How can the same principle be a good idea in 2002 and a bad idea in 2019?

Agile 99

Agile Underperforming Technical Team Software Review Technical Review 99

Project Management Hacks

FEBRUARY 23, 2016

Out of college with a BBA in information technology I started on a help desk providing 2nd and 3rd level support for Cadence, a Silicon Valley software company. I then started managing tech projects while concurrently working on and earning my Master of Science in Information Technology.

Technical Review 53

Technical Review 2015 PMO Information Technology 53

MPUG

OCTOBER 16, 2019

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. And today’s session is eligible for one PMI PDU in the technical category, and the code for claim that is on the screen now, that’s mpugwebnlearn091819.

Agile 40

Agile Technical Review Software Review Engineering 40

MPUG

MAY 18, 2022

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. Cindy is a Microsoft Project trainer and consultant with her business, Four Pillars of Success and has over 25 years of project management experience. Melanie: Hello.

Agile 59

Agile Underperforming Technical Team Software Review Cadence 59

Workamajig

JANUARY 11, 2021

The agile approach is usually used in software projects where the scope is not always known and adaptability is prioritized. Authorization Points: Specific points during the course of a project at which the sponsor reviews the business case and approves the project onwards. All work is divided into short bursts called "sprints".

Underperforming Technical Team 78

Underperforming Technical Team Project Life Cycle Estimate Risk Management 78