Digite

JUNE 13, 2018

Anderson best articulated its application to software development, in 2013, in the foundational book Kanban: Successful Evolutionary Change for Your Technology Business, and its adoption hasn’t been as universal as Scrum’s during the early days of Agile software development. The Cool Power of WIP Limits.

Agile 110

Agile Technical Review Cadence Software Review 110

Leading Agile

AUGUST 19, 2020

And so, from how we do governance and how we do project planning and how we do organizational structure, all those kinds of things, right, so there’s this big hop. Because those are the things that fundamentally get in the way how we govern, right, how we deal with cross cutting concerns. They pull a chunk off the backlog.

Agile 100

Agile SCRUM Governance Government 100

Planio

APRIL 24, 2023

Assessing and mitigating project risks 7. Updating project management software to keep their team on track 9. This often involves rounds of training, communications, and some quick fixes/updates as the test team learns more. To initiate the project, James connects with the: Sales team to assess the size of the crypto market.

Development Team Review 78

Development Team Review 2030 Underperforming Technical Team Risk Management 78

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). Governance (#Governance). Agile Software Development (#ASD).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Leading Agile

MARCH 17, 2021

And I was working for this VP that was like really super cool, is very into agile and we were coming up with really creative things for like team formation strategies and agile governance, all stuff. And business architecture kind of a nebulous term, but how do you form teams? How do you form teams across the enterprise?

2021 62

2021 Agile Underperforming Technical Team SCRUM 62

Scrum.org

SEPTEMBER 19, 2020

There are plenty of opportunities for stakeholders to interact responsibly with a Scrum Team. The two formal Scrum events that come to mind are: Sprint Reviews. The Sprint Review is Empiricism at work: inspect the Product Increment and adapt the Product Backlog. Sprint Reviews are a zone free from death by PowerPoint.

Technical Review 193

Technical Review Software Review Development Team Review Cadence 193

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