Your Team Is An Object; What's its API?
We constantly talk about the value of communication but seldom in terms to which technical teams tend to relate. This session will use the object model, messages and the RESTful architectural style to examine how a development team might interact successfully (or not) with other elements in its system.
We'll discuss systems thinking, message-based communication, software development as a service. To illustrate these ideas we'll map REST actions to team practices.
Outline/structure of the Session
This presentation is predominantly an interactive presentation.
Introduction to thinking in Objects and messages (10 minutes)
Brief review of the RESTful style (5 minutes)
Mapping a team's communication to predictable messages (10 minutes)
Introduction of specific methods that can satisfy external messages (15 minutes)
Examples and discussion of problems and available responses (10 minutes)
Wrap-up and Q+A
Attendees will be able to:
1. Describe team interactions as message-based exchanges
2. Discuss team activity and communication in technical terms
3. Implement methods to improve a team's external communication
People on teams that want to improve interaction with the rest of the organization in which they operate. People outside of teams that are dissatisfied with their interactions with teams.
Some experience with software development teams would be helpful but not essential.
Curiosity about how to improve communication and interaction with technical teams.