D204 - MW Teamwork and Collaboration
What should we consider when Users and Goals of project
creating Technical Standards?
Ways teams work together. For example: Meeting Structure,
What are Process Standards?
Attendees, Making Decisions, Capturing Decisions
Many things at play in a code review: Egos, Code, Author, &
Why should you automate the
Reviewer. Could lead to chaos so let the computer do as
Code Review?
much of it as possible. Focus on the High Conflict/Low
Reward items such as code script.
1) Include atleast 1 positive comment
Tips for leaving comments in 2) Include yourself: why do you want to do this here?
a Code Review? 3) Comment in the form of a question
4) Focus on the code and not the person
1) Don't take it personally
Tips for receiving comments 2) Assume best intent
in a Code Review 3) Pose a follow up question to draw out what the reviewer meant
4) Acknowledge each comment even if it is a simple thumbs up
,Why acknowledge each Let's the reviewer know that you have seen the comment,
comment in a Code Review? acknowledged it, and will make the changes required.
Why should we use more than 1 If you don't, you run the risk of losing your audience with
communication style? poor engagement or of people misunderstanding the
work to be done.
What can you do to make 1) Project Kickoff Mtg
stakeholders feel connected 2) Ask for Feedback on how it is working
to the project right from the
beginning?
1) Layout the details of the project
What should you include in a
Project Kickoff Mtg? 2) Connect the project to how it will benefit stakeholders
3) A heads up on the type of communication they can expect to receive
How does the QA team play 1) They provide the test data and other context that will be used in
the role of both a partner the development
and an adversary in 2) They develop the test cases that will push the software to the limit
Software Testing?
, 1) Use an issues template for bugs:
a) Summary: Explain the issue and keep it short and specific
b) Steps to Reproduce: Only the most basic info needed to reproduce
How can we increase the the issue
effectiveness of the QA role?
c) Expected Results: Describe what you were expecting to happen
d) Actual Results: Describe/show what is actually happening
2) Use a Bug Priority Matrix to identify bugs that will be
potential blockers and ones that are less important.
It is an opportunity to help a new hire adopt the processes
Why is onboarding a new team
and culture of your team. It speeds up the time it takes them
member important?
to be effective and understand the company's expectations
for them.
Do some prep work:
What should happen on day 0 1) Ensure all the tools and systems are setup and ready for Day 1
of onboarding? 2) Prepare an email for the new hire that outlines what
they can expect in their first week.
1) A warm welcome to the team.
2) Link to get access to the Chat platform.
What should be included in the
3) Intro to the Onboarding Buddy.
email prepared on Day 0?
4) Outline of the first week.
What should we consider when Users and Goals of project
creating Technical Standards?
Ways teams work together. For example: Meeting Structure,
What are Process Standards?
Attendees, Making Decisions, Capturing Decisions
Many things at play in a code review: Egos, Code, Author, &
Why should you automate the
Reviewer. Could lead to chaos so let the computer do as
Code Review?
much of it as possible. Focus on the High Conflict/Low
Reward items such as code script.
1) Include atleast 1 positive comment
Tips for leaving comments in 2) Include yourself: why do you want to do this here?
a Code Review? 3) Comment in the form of a question
4) Focus on the code and not the person
1) Don't take it personally
Tips for receiving comments 2) Assume best intent
in a Code Review 3) Pose a follow up question to draw out what the reviewer meant
4) Acknowledge each comment even if it is a simple thumbs up
,Why acknowledge each Let's the reviewer know that you have seen the comment,
comment in a Code Review? acknowledged it, and will make the changes required.
Why should we use more than 1 If you don't, you run the risk of losing your audience with
communication style? poor engagement or of people misunderstanding the
work to be done.
What can you do to make 1) Project Kickoff Mtg
stakeholders feel connected 2) Ask for Feedback on how it is working
to the project right from the
beginning?
1) Layout the details of the project
What should you include in a
Project Kickoff Mtg? 2) Connect the project to how it will benefit stakeholders
3) A heads up on the type of communication they can expect to receive
How does the QA team play 1) They provide the test data and other context that will be used in
the role of both a partner the development
and an adversary in 2) They develop the test cases that will push the software to the limit
Software Testing?
, 1) Use an issues template for bugs:
a) Summary: Explain the issue and keep it short and specific
b) Steps to Reproduce: Only the most basic info needed to reproduce
How can we increase the the issue
effectiveness of the QA role?
c) Expected Results: Describe what you were expecting to happen
d) Actual Results: Describe/show what is actually happening
2) Use a Bug Priority Matrix to identify bugs that will be
potential blockers and ones that are less important.
It is an opportunity to help a new hire adopt the processes
Why is onboarding a new team
and culture of your team. It speeds up the time it takes them
member important?
to be effective and understand the company's expectations
for them.
Do some prep work:
What should happen on day 0 1) Ensure all the tools and systems are setup and ready for Day 1
of onboarding? 2) Prepare an email for the new hire that outlines what
they can expect in their first week.
1) A warm welcome to the team.
2) Link to get access to the Chat platform.
What should be included in the
3) Intro to the Onboarding Buddy.
email prepared on Day 0?
4) Outline of the first week.
