Team Expectations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This applies to project teams, leadership teams! and executive teams. | This applies to project teams, leadership teams! and executive teams. | ||
*Respect | *professionalism and Respect. The key mark of professionalism is clarity of expectations - and ability to communicate these. This includes contingencies. | ||
*Meeting time commitments | *Meeting time commitments. Some available tools are Team Charter, Scrumy, etc, contracts (written and verbal), commitments, timelines, and budgets. | ||
*delivering on promises | *delivering on promises | ||
* creating a collaborative and welcoming environment | * creating a collaborative and welcoming environment | ||
Latest revision as of 18:30, 3 October 2015
This applies to project teams, leadership teams! and executive teams.
- professionalism and Respect. The key mark of professionalism is clarity of expectations - and ability to communicate these. This includes contingencies.
- Meeting time commitments. Some available tools are Team Charter, Scrumy, etc, contracts (written and verbal), commitments, timelines, and budgets.
- delivering on promises
- creating a collaborative and welcoming environment
- Learning from one another
- Being vulnerable. - ultimately opening up your economic models
- Openness to learning
- differentiate between immediate tasks and visioning
- collaborative literacy - both in mechanics of the process and philosophy
- Time binding + economic time binding
- Transparency - your work product is transparent and immediately accessible
- if it's not on the net! it doesn't exist.