Update Communication and Project Management tracks#10
Update Communication and Project Management tracks#10
Conversation
| "Writes effective technical specs outlining approach" | ||
| ], | ||
| examples: [ | ||
| "Wrote the technical spec for Quick User Switching", |
There was a problem hiding this comment.
Based on Medium's descriptions I think requirements analysis and technical design (and getting buy in for the design) fit more under Communication than Project Management.
I've updated it to be more about managing delivery.
| "Collaborates with others with empathy", | ||
| "Asks for help at the appropriate juncture" | ||
| "Asks for help at the appropriate juncture", | ||
| "Practises active listening and suspension of attention", |
| "Estimates small tasks accurately", | ||
| "Delivers tightly-scoped projects efficiently", | ||
| "Writes effective technical specs outlining approach" | ||
| "Ensures stakeholders are aware of current blockers" |
There was a problem hiding this comment.
We can have example about communicating the trade offs during the implementing a project (not sure if PM or Comms)
| "Executed the multiple image uploader for products" | ||
| "Scoped Jira tickets to be dev ready before Sprint Planning", | ||
| "Worked with Product Marketing to communicate roll out while delivering new View Customer design", | ||
| "Executed the multiple image uploader for products", |
There was a problem hiding this comment.
What does executed mean in this context? Project managed it from start to finish?
constants.js
Outdated
| "Gathered multiple stakeholders together to communicate a priority change", | ||
| "Gave notice of upcoming related work in Band Practise" | ||
| "Gave notice of upcoming related work in Band Practise", | ||
| "Created a cross-team Slack channel to collect and update stakeholders for multiple projects" |
There was a problem hiding this comment.
The difference between this example and the other slack channel one for milestone 2 is not that clear to me. Also, creating a slack channel can be a good thing but if you do nothing with it then it's pointless. Would there be a way to change the wording to include something along the lines of "followed through with it" or "used it appropriately to communicate and inform stakeholders of any change"?
| "Delivered basic promotions API endpoint", | ||
| "Delivered new View Customer design", | ||
| "Executed the multiple image uploader for products" | ||
| "Scoped Jira tickets to be dev ready before Sprint Planning", |
There was a problem hiding this comment.
Would be nice to include the notion of multiple tickets that make up a small project?
There was a problem hiding this comment.
Actually, the last example does that :)
There was a problem hiding this comment.
Would you consider replacing "Jira tickets" instances with "stories"?
There was a problem hiding this comment.
i like jira tickets better. stories are a specific thing within jira but there are also bugs and tasks which are important too.
There was a problem hiding this comment.
I see what you mean. I still wonder if there could be a better word. Jira links it to the tool. But what is the concept behind a Jira ticket, in a tool agnostic way?
I am used to call them stories (from Agile lingo) and at a more granular level tasks (which can encompass bugs, enhancements, new features...): "a team does story slicing then scope and estimate the stories..."
Being said, if you keep Jira tickets in the context of Vend, people will understand.
| "Delivered basic promotions API endpoint", | ||
| "Delivered new View Customer design", | ||
| "Executed the multiple image uploader for products" | ||
| "Scoped Jira tickets to be dev ready before Sprint Planning", |
There was a problem hiding this comment.
Would you consider replacing "Jira tickets" instances with "stories"?
constants.js
Outdated
| "Received and integrated critical feedback positively", | ||
| "Created cross-team Slack channel for payments work", | ||
| "Spoke to domain experts before writing spec" | ||
| "Spoke to domain experts before writing spec", |
There was a problem hiding this comment.
"Spoke" might sound a bit uncommitted. What about "collaborated with the the domain experts..." or "Sought domain experts reviews/guidance...".
celine-may
left a comment
celine-may
left a comment
There was a problem hiding this comment.
We're missing a description for the two tracks. These blurbs provide more context and help the reader understand each track.
5 participants
Medium's track guidelines: https://medium.com/s/engineering-growth-framework/engineering-growth-tracks-b1fad620787e
Project Management:
"There is a limit to what people can achieve individually, and coordination of multiple people on a project is very important. We need people that can take large projects, break them down into achievable milestones, manage and delegate scope effectively, and ensure that deadlines are met."
Communication:
"Great communication is central to everything we do at Medium, and without it, most non-trivial efforts would fail. Whether discussing approaches, giving presentations, listening attentively, or managing stakeholders, excellent communication is a key skill. The ability to communicate an idea, and to understand communicated ideas is of critical importance to ensure a well-aligned, agile team."
Let's discuss.