• Why PMs should love CI, part 3: Prioritizing the code that’s needed, not the code they know

    Continuous Integration is often presented as a “dev team” thing — not something us PMs should worry our pretty little heads about. But CI is good for PMs too, and is more successful when PMs buy in. This is a series about why PMs should care about CI and what they...
  • Why PMs should love CI, part 2: Better software (duh)

    Continuous Integration is often presented as a DevOps concern. This is a series about the benefits for PMs and what they can do to help foster the process in their teams. The first benefit I’ll cover is the same one enjoyed by all stakeholders: better software. We don’t have a...
  • Impact mapping example

    I used Impact Mapping for the first time today to help my team brainstorm about our strategic goals for the year. It’s a technique described in Gojko Adzic’s book of the same name for breaking down goals into concrete deliverables in a way that translates nicely into the “As a ___ I want ___ in order to ____”...
  • Why PMs should love CI

    I love my job as a Program Manager at GameHouse. There are a lot of reasons why — good people on my team, working on interesting problems, opportunities to learn. But that’s been true of most of my past jobs too. When I really dig into why I like my...
  • Virtues of starting sprints mid-week

    Our team switched to a mid-week sprint cycle 14 sprints ago and we love it. Our team consists of six developers (4 in main office, 2 offshore) working in two-week sprints. Our every-other-week meeting schedule is: Wednesday morning: Sprint Review Wednesday afternoon: Backlog Review (PO and SM adjust priorities, finish...