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 228

Software Review Technical Review Planning Manufacturing 228

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. Think of your favorite mobile apps (e.g., What are the principles of SAFe?

Agile 36

Agile Development Team Review Lean Underperforming Technical Team 36

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. Creating Your First Kanban Board.

Agile 110

Agile Technical Review Cadence Software Review 110

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 69

Software Review Software Technical Review Development Team Review 69

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

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? If we don’t do that and we’re actually done then the math of Agile work is at the team level, right? We use it as an enabler of our consulting teams and we have absolutely no commitments to market.

Agile 91

Agile SCRUM Governance Government 91

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