Tag: Management

  • Ep18: TL;DR – Risk/Issue Management

    In this episode Todd talks about the practicalities of Risk/Issue Management, including what risks and issues are, how to gather them, how to log them and how to review them.

  • Ep17: TL;DR: Dependency Management

    In this playbook we provide a recipe on how to identify and manage dependencies. We explain why to do it, how to do it, what good looks like, and the most important dos and don’ts.

  • Ep16: Team Roles – Delivery Manager / Scrum Master

    In this Team Roles episode, Marcel and Todd talk about the role of the Delivery Manager and Scrum Master. We talk about the difference between delivery roles and give practical advice on how to help teams reduce risks, remove blockers and… Deliver! We touch on the importance of 1-on-1 relationships with team members, the importance of servant leadership, project awareness, project management tooling, risk management, good project hygiene and how to become a delivery manager.

  • Ep15: Should we allow FE and BE stories?

    In this episode Swathi Poddar and I are talking about a thing we used to fight about: Should we or Shouldn’t we allow frontend and backend specific user stories? Surely, stories should describe features, something that delivers value? But what, if there was a public API? And if it turns out that API also fed a GUI frontend? And what if your team simply demanded it as it made their lives easier?

  • Ep14: Assigning teams to features or services

    In this episode Swathi Poddar and I are talking about a topic very close to our heart: how do we best assign work to our teams? Do we have clear ownership of features or services, and if so, what do we do with the ‘shared’ service we’ll invariably encounter? Are such services commonly owned, can anyone mess with them, or are we keeping them under tight guard, and we ask: ‘Who owns the frontend?’ Expect an interesting, possibly controversial discussion...

  • Ep13: Team Roles – User Research

    In our continued exploration into Team Roles, in this episode we talk to Erica Kucharczyk about the role of User Research. This is a role that is frequently overlooked, but can pay off huge dividends in the long run if quality research is incorporated into your development cycle. We discuss how research helps teams validate their value proposition, the value of user research, the process of designing, running and analyzing tests, Qualitative vs Quantitative, how to get into user research and what good looks like. So, get out there and do some research!

  • Ep12: What if WE Were the Client – Selecting Software Suppliers as a Startup

    In our “If WE were the Client” series we engage in some wishful thinking, turning the situation on its head and talk about all the things we would do and change if we were looking for or working with software suppliers. In this first episode we discuss what Startups should think about when selecting and working with software suppliers.

  • Ep11: TL;DR: Status Reports

    In this TL;DR episode Todd talks about Status Reporting. Status Reports don’t always have to be a chore, in fact it can be a great communication tool if you focus on your audience and quality, concise content.

  • Ep10: TL;DR: Backlogs

    Most software delivery use a story backlog to manage delivery: effectively a list of things to delivery. But often the backlog is at best a mess, at worst confusing and misleading. A good backlog provides structure and facilitates delivery, a bad one adds confusion and inefficiencies. Here is our 5 minute fix to help you optimise your backlog.

  • Ep09: TL;DR: Story Mapping

    Story mapping is maybe the easiest tool to quickly and reliably elicit requirements. It’s my default that always delivers reliable results, not matter the situation. Here is our 5 minute how-to.