Effective Team Communications
Introduction
Every software development project needs to communicate with a variety of stakeholders for multiple purposes across many aspects of the project. This lesson will discuss the stakeholders and the project aspects. It will be important to know what is of importance to each stakeholder. You will use some tools to facilitate your internal team communications.
Learning Outcomes
- Identify the stakeholders for a software development project
- Describe the interest that each stakeholder has in the project
- Describe the practices that support communication across various aspects of a software development project
- Describe the purpose of a daily standup meeting
- Identify common gotchas with the daily standup
Study Resources
For your study of this topic, use some of these resources.
Video Lessons
- Having daily stand-up meetings (4m 33s)
- Reporting status at standups (3m 22s)
- Agile Simulation - Part 20 | The Daily Standup | Agile Videos (10m 31s)
- Identify the project stakeholders (3m 16s)
Web Articles and Blogs
- 6 basic things you shouldn’t be doing during daily stand-up
- 7 Mistakes During the Daily Stand-up Meeting
- Stakeholders on Software Delivery Projects
- Are developers a stakeholder in the system
- Stakeholders in Project Management
- Martin Fowler: It’s Not Just Standing Up: Patterns for Daily Standup Meetings
- Mountain Goat: Daily Scrum Meeting
Books
- Chapter 4 - Roles, Rights, and Responsibilities - The DAD Roles in Disciplined Agile Delivery: A Practitioner’s Guide to Agile Software Delivery in the Enterprise by Scott Ambler and Mark Lines available on O’Reilly through the RIT library.