Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a work estimate section to the template #402

Merged
merged 4 commits into from
Nov 29, 2023

Conversation

basil
Copy link
Member

@basil basil commented Oct 31, 2023

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.

@basil basil requested a review from a team as a code owner October 31, 2023 18:32
Copy link
Contributor

@MarkEWaite MarkEWaite left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a good addition to the JEP process. @timja as the other active JEP editor, are you OK with the addition?

I'll adapt #400 to include the recent JEP improvements

@timja
Copy link
Member

timja commented Nov 9, 2023

I think this is a good addition to the JEP process. @timja as the other active JEP editor, are you OK with the addition?

I'll adapt #400 to include the recent JEP improvements

I'm ok with this adaptation if there's a reference implementation, if you add it, then +1 on this.

@basil basil requested a review from timja November 9, 2023 18:47
@timja timja merged commit 1704721 into jenkinsci:master Nov 29, 2023
@basil basil deleted the work-estimate branch November 29, 2023 21:01
@lemeurherve
Copy link
Member

FTR, I've also started working on a JEP for jenkins-infra/helpdesk#2649 including this section.

@timja
Copy link
Member

timja commented Nov 29, 2023

shouldn't that be an IEP? https://github.com/jenkins-infra/iep

@lemeurherve
Copy link
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants