Work/value not deployed to production

arctangent-nhsuk / the-way-we-work

0 stars 2 forks source link

Work/value not deployed to production #15

Open arctangent opened 3 years ago

arctangent commented 3 years ago

In section 1.4:

The leadership team will monitor how often developers are able to contribute code which is deployed to production.

Feedback:

Developers are often delivering significant value by doing spike work, proof of concepts, documentation, etc, none of which would be deployed to production.

arctangent commented 3 years ago

I don't think the assumption that none of this is deployed is correct, because:

Spikes and POCs should be part of production code, but feature-toggled off
Documentation should be close to code i.e. in the repository

Proposed action:

Communicate the above to developers
Explore concept of Value Chain and non-value-added activities in coaching sessions
Agile Manifesto has 12 principles, one of which is: "Working software is the primary measure of progress."

sikanderakbarali commented 3 years ago

The spike or POCs will still get pushed up in the pipeline to a review branch for you to test. We will be able to see that and each spike/POC you work on will have a jira ticket assigned to it which we we will be able to view

SeanCraig commented 3 years ago

I think there may be an underlying issue re monitoring here. Maybe we need to address where this spike/poc work is done? What we don't want is lots of unplanned time being devoted to work that is never deployed.