This document discusses team and project leadership. It introduces the team and describes using a Team Canvas to define individual strengths, goals, values and ideas. It recommends establishing Objectives and Key Results (OKRs) to set quantitative and qualitative goals in areas like learning and skills development. Examples of tips for project leadership are given, such as bringing people together, encouraging safe discussion, and modeling good behavior. Scrum methods like planning, demos and retrospectives are suggested to structure projects. The importance of understanding stakeholders and challenges is emphasized, as well as leading confidently and questioning assumptions.

1. TEAM & PROJECT
LEADERSHIP
DECEMBER 2022

2. INTRODUCTION
• University • Career

3. INTRODUCTION
• Role
• Technology projects
• Problem space
• Ideation
• Prioritise
• Delivery

4. TEAM LEADERSHIP

5. START WITH THE INDIVIDUAL

6. START WITH THE INDIVIDUAL
Ability
Motivatio
n
1
2
3
4

7. TEAM CANVAS
• Who are we?
• Individual strengths
• Individual goals
• Purpose of the community
• Values and culture
• Blue sky thinking

8. OKRS
• Objective
• Goal
• Qualitative
• KR
• Can be assessed
• Quantitative
• 1 or more per objective
• Ambition is to achieve at
least good
• BA objectives:
• #1 Increase the capability
of business analysts
• #2 Share our successes
• # 3 Have fun!

9. OKRS
Objective 1 - Increase the capability of business analysts in our hub
Key result - Formal learning
The number of BCS certifications completed by September 2018:
2 = good
3 = very good
4 = great
Key result - Informal learning
The number of lunch and learns run by September 2018:
6 = good
8 = very good
12 = great
Key result - Peer assessments
All business analysts will increase their capabilities by September 2018 by:
1 capability = good
2 capabilities = very good
3 capabilities = great

10. EXAMPLES

11. TIPS
#1 - Bring people with you
#2 - Encourage & support people
#3 - Have fun
#4 – Safe space
#5 - Exclusive

12. PROJECT LEADERSHIP

13. START WITH SOME STRUCTURE
• Ways of working
• Responsibility:
• Responsible
• Deliverables
• Need
• ABC:
• Artefacts
• Behaviour
• Ceremonies

14. SCRUM
• Product roadmap / backlog
• 2 weeks:
• Planning = buy-in
• Demo = stakeholder
• Retro = team morale
• Every day:
• Standup

15. OWN THE PROBLEM NOT THE SOLUTION
• User research
• Assign an area
• Work in the open
• Outcomes not solutions
• Roadmap - capabilities vs
integrations

16. MANAGING STAKEHOLDERS
• Identify stakeholders:
• Need to do work
• Knowledge
• Involved in decisions
• Affected
• Power / interest grid
• Ownership and commitment

17. LEADERSHIP
• Lead from the front
• Project confidence
• Assume good intent
• Model behaviour
• Challenge the status quo

18. THANKS!!
• Team canvas = https://dwpdigital.blog.gov.uk/2017/06/30/helping-teams-identify-their-key-metrics/
• Team canvas = http://theteamcanvas.com/
• OKRs = https://www.techtarget.com/searchhrsoftware/definition/OKRs-Objectives-and-Key-Results
• ORKs = https://dwpdigital.blog.gov.uk/2018/03/16/setting-community-goals-using-objectives-and-key-results/
• Ways of working canvas = https://medium.com/@CharlesRowat/the-ways-of-working-canvas-651f8f44f288
• Ways of working = https://miro.com/miroverse/team-work-canvas/
• Scrum = https://www.mountaingoatsoftware.com/agile/scrum
• Retros = https://easyretro.io/retrospective-ideas/
• Start with why (leadership) = https://simonsinek.com/books/start-with-why/
• Impact mapping (turn goals into ideas) = impactmapping.org