Skip to content
This repository has been archived by the owner on Dec 28, 2023. It is now read-only.

Update Communication and Project Management tracks #10

Open
wants to merge 10 commits into
base: master
Choose a base branch
from
37 changes: 22 additions & 15 deletions constants.js
Original file line number Diff line number Diff line change
Expand Up @@ -382,10 +382,10 @@ export const tracks: Tracks = {
signals: [
bandyson marked this conversation as resolved.
Show resolved Hide resolved
"Estimates small tasks accurately",
"Delivers tightly-scoped projects efficiently",
"Writes effective technical specs outlining approach"
"Ensures stakeholders are aware of current blockers"

Choose a reason for hiding this comment

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

We can have example about communicating the trade offs during the implementing a project (not sure if PM or Comms)

],
examples: [
"Wrote the technical spec for Quick User Switching",
Copy link
Author

Choose a reason for hiding this comment

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

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.

"Effectively estimated assigned Jira tickets for Quick User Switching",
"Delivered low stock warning for iOS",
"Delivered new User badge"
]
Expand All @@ -399,8 +399,10 @@ export const tracks: Tracks = {
],
examples: [
"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",

Choose a reason for hiding this comment

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

Would be nice to include the notion of multiple tickets that make up a small project?

Copy link

@celine-may celine-may Nov 22, 2018

Choose a reason for hiding this comment

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

Actually, the last example does that :)

Copy link

@rlopes rlopes Nov 23, 2018

Choose a reason for hiding this comment

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

Would you consider replacing "Jira tickets" instances with "stories"?

Copy link
Author

@bandyson bandyson Dec 6, 2018

Choose a reason for hiding this comment

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

i like jira tickets better. stories are a specific thing within jira but there are also bugs and tasks which are important too.

Copy link

@rlopes rlopes Dec 6, 2018

Choose a reason for hiding this comment

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

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.

"Worked with Product Marketing to communicate roll out while delivering new View Customer design",
"Executed the multiple image uploader for products",
Copy link

@tenitski tenitski Nov 21, 2018

Choose a reason for hiding this comment

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

What does executed mean in this context? Project managed it from start to finish?

"Broke down Home Dashboard Integrated Payment Recommendations into tickets with estimations"
]
},
{
Expand All @@ -413,7 +415,8 @@ export const tracks: Tracks = {
examples: [
"Ran project retro to assess improvement opportunities",
"Completed launch checklist unprompted for well controlled rollout",
"Facilitated project kickoff meeting to get buy-in"
"Facilitated project kickoff meeting to get buy-in",
"Worked with Marketing to define scope and delivery timelines for Crafty CMS"
]
},
{
Expand All @@ -425,8 +428,8 @@ export const tracks: Tracks = {
],
examples: [
"Oversaw delivery of Promotions",
"Built the features service",
"Involved marketing, legal, and appropriate functions at project start"
"Managed the building of the features service",
"Co-ordinated the different requirements of marketing, legal, and appropriate functions throughout the GDPR project"
]
},
{
Expand Down Expand Up @@ -454,9 +457,11 @@ export const tracks: Tracks = {
{
summary: "Communicates effectively to close stakeholders when called upon, and incorporates constructive feedback",
signals: [
"Communicates project status clearly and effectively",
"Communicates status of assigned tasks clearly and effectively",
"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",
Copy link
Author

Choose a reason for hiding this comment

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

moved from 2 to 1.

"Provides the appropriate amount of information and technical detail based on parties being comunicated with"
],
examples: [
"Updated oncall-engineers before running a resource-intensive task.",
Expand All @@ -467,27 +472,29 @@ export const tracks: Tracks = {
{
summary: "Communicates with the wider team appropriately, focusing on timeliness and good quality conversations",
signals: [
"Practises active listening and suspension of attention",
"Ensures stakeholders are aware of current blockers",
"Chooses the appropriate tools for accurate and timely communication"
"Chooses the appropriate tools for accurate and timely communication",
"Writes effective technical specs outlining approach",
"Identifies and proactively involves the appropriate people to reach a consensus on a technical decision"
],
examples: [
"Received and integrated critical feedback positively",
"Created cross-team Slack channel for payments work",
"Spoke to domain experts before writing spec"
"Collaborated with domain experts before writing spec",
"Proactively recorded decisions in the project decision log after a meeting"
]
},
{
summary: "Proactively shares information, actively solicits feedback, and facilitates communication for multiple stakeholders",
signals: [
"Resolves communication difficulties between others",
"Anticipates and shares schedule deviations in plenty of time",
"Manages project stakeholder expectations effectively"
"Manages project stakeholder expectations across teams effectively"
],
examples: [
"Directed team response effectively during outages",
"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",
"Anticipated impact of design changes and worked with design and product to design a solution while meeting the committed release date."
]
},
{
Expand Down