This repository has been archived by the owner on Dec 28, 2023. It is now read-only.
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.
Update Communication and Project Management tracks #10
base: master
Are you sure you want to change the base?
Update Communication and Project Management tracks #10
Changes from all commits
d662ac2
11adfb6
561d08f
6a6ac16
1a11e81
f150f5b
be26e08
730f7d0
b3964f2
9bf2c69
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
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)
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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 :)
There was a problem hiding this comment.
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"?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.