|
|
|
|
|
|
by Zombieball
3036 days ago
|
|
|
What tooling are you referring to? I skimmed through other comments and didn’t notice any concrete examples? Do you envision something like project planning software? I think a key point of a good manager is also people development. But I imagine engineers could self-organize mentorships. |
|
|
1. Product Direction
a. Source in Initiatives (road map) , Product stories managed by Product/Project manager, Sr. Manager and Director thus providing inputs on the business aspects and requirements.
b. Tech Lead/Principal/Sr.Engineer provides feedback on 1a.)
2. Delivery Mgmt
a. Stories will be mapped to Features for which the Architecture/Design (done by Sr.Engineers) would be reviewed/voted by team. Override of a technical approach (with justification) can be done by Principal/Sr.Engineer, however, this could be escalated to the Sr. Manager / Director by other team members (anonymously) . Sr.Mgr and Director would also chip in and provide their inputs if required and accordingly lead to a resolution based on data points, pros/cons etc. In this way, conflicts or ego issues can be minimized.
b. Feature will be prioritized by Tech Lead / Sr. Engineer based on comments from team or directly proceed to c)
c)Feature will be assigned to an Engineer for implementation
d)Feature will be verified by QA as well as Business lead/user post deployment or software release
e)Delivery feedback to be provided by the Product manager and Business user, this will be used to provide opportunity for improvement and/or appreciation of the effort (and hence motivation).