Add a work estimate section to the template#402
Merged
Conversation
MarkEWaite
approved these changes
Nov 9, 2023
Member
timja
approved these changes
Nov 9, 2023
Member
|
FTR, I've also started working on a JEP for jenkins-infra/helpdesk#2649 including this section. |
Member
|
shouldn't that be an IEP? https://github.com/jenkins-infra/iep |
Member
|
@timja: after discussing it with @dduportal and as we'd like to establish a contract with Core to follow UC redirections to mirrors, we think the scope of this project is more large than an IEP. This can be challenged though. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Jenkins project does not have dedicated project managers, so architects ought to consider the project management implications of their proposals. My personal experience has been that considering these implications at the time of project design can significantly improve the resulting design by identifying task dependency bottlenecks (and forcing the author to think about if and how they can be resolved) as well as staffing requirements (and forcing the author to revise the design if it is impractical within the realities of staffing constraints). Most importantly, the act of breaking down a prototype into the tasks needed to productize it serves as a forcing function to ensure that the prototype is complete enough to serve its purpose of informing a design. If a prototype is so preliminary that one cannot clearly envision the tasks needed to complete it, then that is an indication that the prototype has failed to explore all the relevant issues in enough depth and that the design is likely to contain gaps and/or errors in judgment.
Testing done
I have been using these ideas for years in other roles and communities.