Leading Agile

JULY 28, 2022

This means they know the scope of what’s required, how to complete it, and when it needs to be delivered. They can negotiate the amount of work they accept into their sprint during sprint planning based on their team’s past velocity. When the delivery rate of work is slower than you think, it messes up the team’s velocity.

Agile 125

Agile Technical Review Cadence Software Review 125

Planio

JULY 4, 2022

Agile ceremonies are the fuel that keeps your development team moving forward. Agile ceremonies get abandoned when teams stop seeing the value in them. (And Sprint review ceremony. Each morning, team members discuss what they worked on yesterday, what they’re doing today, and what’s blocking them from moving forward.

Agile 88

Agile Technical Review Development Team Review Software Review 88

Planview

JUNE 1, 2021

It can be challenging to expand Agile practices beyond IT and development teams. Hosted by CITF, the UK’s leading membership organization for technology professionals, the webinar includes our insights and recommendations on extending Agile practices. Where do you begin? What needs to change?

Cadence 148

Cadence Logistics Lean Agile 148

Planio

AUGUST 9, 2021

How to write a project schedule in 9 steps. Monday.com: Best for non-technical teams. In this guide, we’ll teach you how to write a project schedule, keep it updated throughout the project lifecycle , and use it to get buy-in on scope and resources. How is a project schedule different from a project plan or SOW?

Software Review 78

Software Review Technical Review Estimate Agile 78

Digite

JUNE 13, 2018

She also shows you how to design your first Kanban Board, with examples. Shows how a marketing team can benefit by Visualizing work on a Kanban Board! But, for teams that chafe under the strictures of the Scrum process, Kanban can be a freeing alternative. Next, fill in what happens on the team between those two points.

Agile 110

Agile Technical Review Cadence Software Review 110

Scrum.org

JANUARY 10, 2021

Once you accept this, and quality becomes non-negotiable, your Dev e lopers can focus on creating usable increments of working software. Without a regular cadence of delivery of working software any belief that you will get a usable increment is misguided at best. Professional Developers create working software.

Software Review 230

Software Review Technical Review Planning Manufacturing 230

Planio

APRIL 24, 2023

Assessing and mitigating project risks 7. Updating project management software to keep their team on track 9. Researching and validating project ideas During the project initiation phase, a project manager works to validate ideas and assess whether they’re worth proceeding with. Researching and validating project ideas 2.

Development Team Review 78

Development Team Review 2030 Underperforming Technical Team Risk Management 78

Digite

MARCH 12, 2018

That is, does the question below, which I answered on a technical forum recently, describe a situation you might be facing or may have faced in the past? These may seem like three distinct questions, but are, in my mind one: how to structure the Kanban board – around people, or around tasks? Dev Lane for the main dev activity.

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

Planio

AUGUST 1, 2022

For most development teams and startups, ‘becoming Agile’ starts and ends with how you build software. But a full Agile transformation isn’t just about the development process you use — it’s a way to bring creativity, innovation, and lean operations to every aspect of your business.

Agile 78

Agile Technical Review Leadership Infrastructure 78

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. I advise to start finding one person to be the single Product Owner for all teams. The Product Owner should develop an inspiring vision and a plan to make it happen.

Underperforming Technical Team 153

Underperforming Technical Team SCRUM Development Team Review Software Review 153

Leading Agile

AUGUST 19, 2020

In this webinar, we discuss how to create more predictability so we can meet our commitments to customers, and build trust with everyone from internal stakeholders, to customers, to our entire market. And so, predictability is really all about figuring out how to make and meet commitments and how to do what you say you’re going to do.

Agile 100

Agile SCRUM Governance Government 100

Wrike

FEBRUARY 20, 2023

It is especially useful for large-scale enterprise teams that work on extensive, complex, long-term projects, as it helps them stay on track and meet acceptable standards throughout every stage of the project. We’ll also share how to determine if SAFe is right for your company and when best to use the framework.

Agile 36

Agile Development Team Review Lean Underperforming Technical Team 36

Scrum.org

APRIL 30, 2019

They use practices, people, and technology to find a way to overcome their disability of delivering value to market too slowly. In the beginning, they have trouble seeing how it will work in their current day to day environment. More dependencies surface when people realize they have team members assigned to two or more projects.

Agile 129

Agile Cadence Technical Review Development Team Review 129

Herding Cats

APRIL 16, 2019

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Technical Performance Measures (#TPM). Cost, Schedule, and Technical Performance Management (#CSTPM). Product Development (#ProdDev). Agile Software Development (#ASD). Business, Technical, Systems, Risk, and Project Management.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

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

And business architecture kind of a nebulous term, but how do you form teams? How do you form teams across the enterprise? What do you organize those teams around? What responsibilities do those teams have? Do they own the technology or do they have dependencies with tons of teams around them?

2021 62

2021 Agile Underperforming Technical Team SCRUM 62

Scrum.org

SEPTEMBER 19, 2020

Deciding early on how to communicate with internal stakeholders and win their proverbial hearts & minds often makes the difference between “doing agile” and “becoming agile” in the end. There are plenty of opportunities for stakeholders to interact responsibly with a Scrum Team. Sprint Reviews are a zone free from death by PowerPoint.

Technical Review 210

Technical Review Software Review Development Team Review Cadence 210

Leading Agile

AUGUST 20, 2018

An unattended software delivery pipeline frees technical staff to spend more time on value-add activities rather than tediously performing repetitive tasks by hand, such as. Reviewing code by eyeballing it to ensure compliance with coding standards. Handling merges of code changes made by more than one person.

Software Review 78

Software Review Software Technical Review Development Team Review 78