Crossing Over: Implementing Scrum from the Dark Side
Upcoming SlideShare
Loading in...5
×
 

Crossing Over: Implementing Scrum from the Dark Side

on

  • 302 views

Talk given at SUGSA on 8 May 2014. A personal reflection on making the transition from being an Agile team member, to being an Agile manager. Includes mistakes made and lessons learnt in the process ...

Talk given at SUGSA on 8 May 2014. A personal reflection on making the transition from being an Agile team member, to being an Agile manager. Includes mistakes made and lessons learnt in the process of introducing Agile (Scrum) to the team I now manage.

Statistics

Views

Total Views
302
Views on SlideShare
289
Embed Views
13

Actions

Likes
0
Downloads
0
Comments
0

3 Embeds 13

https://twitter.com 6
http://localhost 4
http://www.slideee.com 3

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Crossing Over: Implementing Scrum from the Dark Side Crossing Over: Implementing Scrum from the Dark Side Presentation Transcript

  • Maritza van den Heuvel Beyond Agile – Tales of Continuous Improvement http://scrumfamily.wordpress.com @maritzavdh
  • In a galaxy far, far away …
  • Linguistics Research Technical Writing Testing Support Product Owner Product Manager “NOT TEAM”
  • • the process wasn’t mine anymore • the “how” wasn’t my job anymore • new responsibilities for “what” • new responsibilities for delivery • relying on the team to get things done • feeling helpless – I had to trust more deeply • feeling sad – I embracedAgile! 
  • • 3 years - adjusted to the new conditions • started training my jedi mind control (otherwise known as influencing skills) • needed new challenges and growth (plus I wanted to change the world!) • brief sidestep into a similar role • Pearson: setting up my own team
  • (NOT) Episode III
  • - linear hierarchies - top-down decision-making - accepting a given system, not creating it
  • - simple and flat team structure - visible and transparent reporting - decisions at the lowest responsible level - expecting team to engage with process - team commitment to focus delivery - team collaboration as a shared value - Agile/Lean software development
  • - No immediate need – digital support - Used Personal Kanban as talking point - Shared articles, blogs and links - Introduced LeanKit Kanban - #leadershipfail - Mistake: Individual work, NotTeam - Mistake:Tool over Process & Principles - Mistake:Too subtle and informal - Regroup!
  • - major team role change & new members - explicit software focus and structure - open with team about Agile intentions - explicit team agreement to learn and try “help me, to help you” - First Change: Board & Daily Standups - Next Step: Overview/IntroTraining - Shock:They hated Kanban!Chose Scrum
  • - believed that Kanban would be chosen - obsessed and analyzed for a week - proposed some changes to the training - realization: team wasn’t ready - they chose what *they* needed - structure - team cohesion - progress check points
  • - Full team ScrumTraining and Kickstart - Ongoing coaching support - Shared ScrumMaster responsibilities - Two POs, collating work across multiple project backlogs into a single sprint backlog every two weeks - So far so good … Mostly Positive Results
  • - Asking & expecting team to solve problems -Accepting & valuing team process solutions - Challenging & interrogating team thinking -Withdrawing from Scrum meetings - Supporting individuals with new skills - “Guide on the Side” - Work tools, environment, knowledge, funds - Insulation and Business Communication
  • • observing - seeing the work honestly • questioning - interrogating the work • applying - courage to try something new • evaluate - interpret and adjust "seeing the system" - lack of contextual awareness, lack of ability to change things, waiting for somebody to tell me the answer ~ Bob Marshall
  • Maritza van den Heuvel • @maritzavdh #edtech #agile #lean #scrum • http://scrumfamily.wordpress.com • Beyond Agile - Tales of Continuous Improvement • Innovation Lab Director: Pearson South Africa