Tvivla have done training since 1990 starting with general PC knowledge and effective usage of Microsoft Office and Lotus Notes. Today we offer online trainings with a strong focus on Agendo discunt (latin for leaning by doing). Our sessions are approx 25% theory plus 75% practice and discussions. Another word for this concept is flipped classrom where we expect the students to do challenges (homework) in between sessions to enforce learning and avoid the Ebinghaus forgetting curve.
Tvivla steps
- Prepare content – make sure the topic is prepared and tailored for the students and their organisation. Ex: The trainers study the organisation and students skills on the topic and create the material.
- Inspire – make sure students are interested in the topic prior session. Ex. Send a link to a film on the topic.
- Teach the basics – what is it and why should we care? Minimize this theory part in favor of practice. Ex: 1-5 Powerpoint slides.
- Discuss – The students discuss what this means to them and become engaged. Ex: Discuss 2 and 2 the merge groups to 4 and 4.
- Create actions – For the topic and how we can implement this in reallity. Ex: Set up a war room.
- Practice – Try the action in the small groups as a safe space. Ex: Make a prototype and a role play around it.
- Feedback – from the other class on the practice.
- Challenge – Make sure its stick when you are back home. Report back to trainers within x weeks on the progress/outcome.
Our sessions are always facilitated by two trainers. One of these trainers can be your own Scrum masters, Agile coaches or Product owners so we in paralell train your future trainers and keep the knowlegde in house.
Training is just one part of your upskilling the knowledge. We also recommend a coaching effort in parallell aligned with the Toyota kata approach where improvement and mentorship follow the actual training. Reach out to us for more information.
Smorgasboard
Here what we recommend as trainings for certain roles:
| Session/Topic | Objective | Content | PO | ScM | Team | Leaders |
| Team phase intro | Understanding the content and format of the team phase and the tools used and getting to know eachother. | Presentations, Tools, resources, purpose, schedule, learning curve, flipped classroom, session distribution, admin, working agreement, 70-20-10 | x | x | x | x |
| Agile basics | Understanding why we want agility | Agile, Scrum, Scrum sessions, Kanban, Flow, Scaling | x | x | x | x |
| Psychological safety | A quick look into why PS matters and highlighting the need | ISO45003, PS assessment, Imposter syndrome, learning, management by fear | x | x | x | x |
| The team | Essentials for getting your team through the forming (first) stage and prepare for noring (second) stage in team evolution. | Autonomy, Tuckman stages, AMA, Playbook, working agreement, T-shape, slogan, logo, skills mapping, meetings | x | x | x | x |
| Change | Useful tools for understanding change management | PDCA, Kotter, Management 3.0, ADKAR, Kaizen/Kaikaku | x | x | x | |
| Backlog | How we make sure we are working on the right thing | Prio, estimate, slicing, DoD, DoR, INVEST, refinement, features, stories, VSJF, backlog balance, technical debt | x | x | x | |
| Leadership | Know how leaders differ from managers | Delegation, vision, empowerment, feedback, trust, leading by example, leadership styles, conscent | x | x | x | |
| Discovery | Understand how great requirements are born | Lean UX, Deisgn sprint, MVP, A3, hypothesis, prototyping, INVEST, spike | x | x | ||
| Events | Understand how diffrent events and meetings are used and facilitated | Gallery walk, open space, lean coffee, big room planning, scrum meetings, all hands | x | x | x | x |
| Facilitation | Having a framework for organizing and running events | Prep, intro, topic, outro, aftermath, rethoric, six thinking hats | x | x | x | |
| Metrics | Know how we measure progress and where we are going | KPI, OKR, AMA, mission, vision, velocity, predictability | x | x | x | x |
| Environment | Understanding of the team externals | Stakeholders, dependencies, customers, personas, scrum of scrums | x | x | x | |
| Improvement | Having a tool for continuous improvment | Retro types, sphere of influence, PDCA, SWOT | x | x | x | |
| Tools | Understand what tool to use for what purpose. | Miro, Sharepoint, WIKI, Teams, Azure devops | x | x | x | |
| Roles and responsibilities | Know expectations (and gaps) on key roles | Gap analysis, Scrum master, Product owner, Team, RASCI | x | x | x | x |
| Visualization | Get useful tools for showing team status etc | Workflow, dependencies, mood board, info radiator, homepage, metrics | x | |||
| Coaching | Understanding of the diffrent coaching stances | Facilitation, Mentoring, Education, Coaching | x | x | x | |
| The Kanban board | How to use and configure a Kanban board | WIP limit, committment, pairing, pull, lead time, cycle time, flow. | x | x | x | x |
| Product vs Projects | Understanding on when to use which approach | Flipped triangle, value streams, bimodality | x | x | ||
| Agile Portfolio Management | How to connect strategy with delivery | Lean canvas, MVP, Impact mapping, Story mapping, Hypothesis, dashboards, flight levels | x | x | x | |
| Planning | Understanding of how to do planning on different levels and plan a sprint. | The planning onion, roadmap, vision, epic, feature, story, sprint goal | x | x | x | x |
| Team topologies | Understanding of how teams interact with eachother | Team of teams, Team types, Team forming, Interactions, Team API, FAMILY model | x | |||
| Systems thinking | Understanding on how complexity impacts our work and our systems. | systems thinking, complexity theory, cynefin, system of constratints | x | |||
| Culture | Get an understanding on how culture is a key aspect in agility | Hofstaede index, diversity, distributed teams, proxy PO, core values | x | x | x | x |
| BizDevOps | Understand how we want to work with the whole value chain in the team | Requirements, Workitems, Monitoring, testing, development, maintenance, tech debt, defects | x | x | x | x |
| The product owner | As a PO to understand the expectations on the role | Product backlog, Planning, Leadership, GAP analysis. | x | |||
| The Scrum master | As a ScM/TL to understand the expectations on this role | Sprint backlog, impediments, team building | x | |||
| PO/ScM training | As a PO/ScM i get the basics for being comfortable in my role | Generic PO/ScM training | x | x | ||
| Guilds | To understand the need for guilds and how to set them up | Tool, meetings, work agreement, critical mass | x | x | x | x |
| Mission | To understand what our purpose as a team is | Mission, vision, objectives, slogan, logo, values | x | x | x | x |
| Refinement | To create great stories for the sprint | Story, feature, slicing, ranking, estimation, velocity | x | x | x |