“How’s the product looking?”
Everyone from the CEO to the Technical Support Analysts wants to know. Learn the dangers for “hallway reporting” and the best responses.
What’s the #1 mistake techies make in communicating with the team and upper management.? We’ve got you covered!
Understand who your audience is, what they need to know (and why) and how to get to the point.
We’ll take a look at written reports and give you a simple, easy to use format. You’ll also learn what makes a report boring and irrelevant.
Got fears that the project is running behind, needs more people or another feature to really be useful? We’ll talk about how to use project data to convey your point to management.
The biggest risk to your project is the fact that your entire team comes from different companies and different educational backgrounds. You may think you are all speaking the same language but behind the words are:
- Varying expectations
- Differing definitions of the same term
- Differing experiences in the same methodology (ie: Agile)
In Communication Skills for Technical People you will learn to:
- Think like a financial stakeholder in the project. This is the ultimate bottom line.
- Remove risky assumptions and begin to operate like a business and identify all the inputs andoutputs from your internal clients and vendors including the level of quality of each of the deliverables.
- Communicate concisely in meetings and in written reports.
- Easily get the information you need to get your job done and meet your deadlines.
Learning Objectives
- Explore how to behave in meetings (what to say and what NOT to say)
- Explore the different audiences you have and what information each one is looking for in order to get their job done
- Explore how to summarize and get to the point.
- Discover the memory aids that will help you quickly and easily remember what to say in person,in meetings, in email/weekly reports and in project status reports.
4 Reviews (29 ratings)
Reviews
Prerequisites
- No advanced preparation or prerequisites are required for this course.
- This course assumes that you are working in a software development environment.
- This course assumes the people on the team are normal, healthy people.
- This class does not cover how to deal with difficult people.