Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Clarification on a couple of the topic prompts #2
I recently ran a session using the Team Health prompts, and a few questions had us discussing what we thought the intent of the question was, or some of the wording choices.
We think that "exciting" releases are a bad thing. Releases should ideally be normal and bording.
We were unclear what was meant by the "process for developing" - is this about the delivery process, or about the act of typing into our editors? We went with the former.
Is this about the day-to-day process, or the longer term planning process? We went with the former.
We suggest perhaps changing "developing" to "delivering"?
Thanks, @glenjamin - good points.
I agree that releases should not be A Big Thing. For some orgs "exciting" is a good thing but not all orgs :) . How about "It is easy and straightforward to release a change" ?
Some of the wording is deliberately open to interpretation so that it's useful for different situations. It should be up to the team to decide what angle is most useful for them. My intent with the "process for developing" question was to identify things that get in the way of software development & delivery. How about "how suitable is the process for developing and delivering software?"
I'd be happy with a PR for these two changes - I think they clarify the intent. Thank you for trying out the assessment and the feedback!