Scrum.org

NOVEMBER 7, 2018

To use the leadership styles model we discuss in the Leading SAFe class - the starting point is more of an orchestrating and technical expert kind of leadership stance and the goal should be to evolve towards a more serving the team and the process style over time. SAFe has a cadence at the Team and Program levels.

SCRUM 114

SCRUM Development Team Review Technical Review Cadence 114

Rebel’s Guide to PM

AUGUST 6, 2022

It’s fine to have a different cadence at different points in the project lifecycle. If you are expecting the project oversight committee to make a decision at the meeting, make sure that they have information in advance of your meeting so that they can review the different options. Action review and next steps. Key decisions.

Governance 375

Governance Government Risk Management Technical Review 375

Scrum.org

JANUARY 30, 2023

This article is another excursion into this nascent yet fascinating new technology of generative AI and LLMs and the future of knowledge work. Shall we outsource the effort to one of the big consultancies — McBoston? If technology can pass a Wharton MBA exam , maybe, it deserves some attention. I am no longer sure about that.

ChatGPT 194

ChatGPT Agile Artificial Inteligence Consulting 194

Agilemania

JANUARY 19, 2022

Go for the SPC exam only if you truly wish to become a SAFe Program Consultant. If you aspire to become an Agile Coach and then need to lead the SAFe implementation in your organization, becoming a SAFe Program Consultant is the right choice. It would be better if you could get someone knowledgeable to review it. Tipping Point

Certification 98

Certification Lean Technical Review Consulting 98

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

MPUG

FEBRUARY 1, 2021

As per PMI, there are three types of PMOs: A supportive PMO largely plays a consultative role such as providing templates, imparting training and coaching, and storing lessons learned across projects. Consulting: Adopting various project management frameworks or methods. Types of PMOs. Multi-Disciplinary. Resourcing.

Agile 94

Agile PMO Technical Review Cadence 94

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

Wrike

APRIL 21, 2023

The Occupational Safety and Health Administration (OSHA) , Information Technology Infrastructure Library (ITIL) , and International Financial Reporting Standards (IFRS) are examples of regulatory agencies that may require certain processes be followed to the letter. Let’s return to our employee onboarding example for some clarity.

Technical Review 36

Technical Review Software Review Cadence Process 36

Project Management Essentials

AUGUST 3, 2019

In my agile training and consulting practice, I have witnessed similar symptoms when an organization is struggling with its agile adoption. Outsourcing is a good option for organizations where technology is not a core or strategic competency. Poorly coded features may be technically complete, but not acceptable.

Underperforming Technical Team 40

Underperforming Technical Team Agile Technical Review Software Review 40

Planio

AUGUST 9, 2021

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. Putting it all together: A free project schedule template for you to use.

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. What would you go do?

Agile 62

Agile Underperforming Technical Team Cadence SCRUM 62

Scrum.org

MARCH 11, 2024

Every activity required to achieve the Product Goal, such as Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, occurs within Sprints. This also applies to refactoring parts of the tech stack, exploring new technology that might be useful, fixing some bugs, or sharing knowledge with fellow teammates.

Technical Review 169

Technical Review Underperforming Technical Team SCRUM Software Review 169

Scoro

OCTOBER 14, 2024

For agencies and consultancies, this usually means checking things like how well your team is managing their tasks, how long tasks are taking, and whether the project costs are sticking to the plan. And may also sync with other tools in your tech stack. Review projects regularly Set up a regular cadence for project monitoring.

Software Review 52

Software Review Technical Review Estimate Underperforming Technical Team 52

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 62

Agile Technical Review SCRUM Engineering 62

Scrum.org

MARCH 28, 2022

All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints. This also applies to refactoring parts of the tech stack, exploring new technology that might be useful, fixing some bugs, or sharing knowledge with fellow teammates.

SCRUM 167

SCRUM Technical Review Software Review Consulting 167

Leading Agile

JANUARY 21, 2021

And what we are is we’re a consultancy that’s focused on doing Agile Transformation specifically. So you do review and retrospective to say, do a burn down chart. So I need a backlog, I need a dedicated team and I need the technical ability to produce a working test and increment at the end of every sprint.

Sustainability 76

Sustainability Agile SCRUM Technical Review 76

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.

SCRUM 94

SCRUM Cadence Lean Underperforming Technical Team 94

Planio

AUGUST 1, 2022

According to research published in Harvard Business Review , nearly 90% of companies struggle to complete Agile transformations — even after successful pilot projects. Technology: Agile organizations need to trust their data and have the infrastructure ready to build and test new ideas rapidly.

Agile 78

Agile Technical Review Leadership Infrastructure 78

Leading Agile

AUGUST 19, 2020

They deliver it, they review it with the product owner, product owner says yes, and then they get to claim the points, right? We use it as an enabler of our consulting teams and we have absolutely no commitments to market. They pull a chunk off the backlog. They go through sprint planning, maybe they decompose the work.

Agile 88

Agile SCRUM Governance Government 88

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 also includes standard Agile recurring events such as sprint planning, reviews, and retrospectives. Synchronized cadence: SAFe Agile uses a consistent rhythm of work called cadence , which includes standard Agile events such as sprint planning, sprint review, and sprint retrospective.

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. He goes, that’s the domain of consultants, that’s the domain of organizations to figure that out. I did a podcast, I guess it wasn’t technically a podcast.

Governance 62

Governance Government SCRUM Agile 62

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

Leading Agile

MARCH 17, 2021

Do they own the technology or do they have dependencies with tons of teams around them? And we experienced that viscerally as a consultancy, but you guys experienced it too. We know that they have ownership over the technology, stack. They don’t have technical dependencies. What do you organize those teams around?

2021 62

2021 Agile Underperforming Technical Team SCRUM 62

Leading Agile

FEBRUARY 11, 2019

Because the recovery phase was not officially recognized (typically due to time reporting rules that prohibited honesty regarding overtime), management missed the opportunity to learn from experience and repeated the death march pattern again and again. When agile consultants advise organizations to form small teams, the problem worsens.

Agile 89

Agile Underperforming Technical Team Software Review Technical Review 89

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

Authorization Points: Specific points during the course of a project at which the sponsor reviews the business case and approves the project onwards. Projects might additional calendars as well to show resource availability, communication cadence, etc. Go") or abandoning it (i.e., "No No Go") at a decision Gate.

Underperforming Technical Team 78

Underperforming Technical Team Project Life Cycle Estimate Risk Management 78