Product Managers, Project Managers, ScrumMasters, and sometimes even Engineering Managers. People whose job is primarily to support developers, and yet often these folks come from a background that includes zero technical experience. Under constant pressure to focus on "feature delivery" by folks from Sales, Marketing, and other various parts of the business, all too often the so-called "non-functional requirements" often fall by the wayside. Things like operability and sustainability can often fall by the wayside if developers aren't given the resources needed to make sure these things are baked in.

But all is not lost. Many of the lessons learned from the DevOps movement can also be used to bring "Product" in-line with both developers and operators. Focusing across specific roles, we will look at the full life-cycle of development, deployment, incident response, and everything in support of that, and that affects planned work and the actual work that gets done. Methods for championing Ops needs while avoiding the classic "sky is falling" pattern of ops management will be looked at, including a look at unplanned work, how it affects your team, and how to make things flow.

Comments

Comments are closed.

Ian Littman at 16:44 on 23 Oct 2019

Solid talk, though font size on slides tended to be a bit small, and ASCII art arrows on a non-monospace font looked askew a time or two. Using boring old normal arrows, or arrows that look like ASCII but are actually images, would've probably given you enough room to bump font sizes. Also didn't realize that the focus of the talk was quite so devops-heavy...which was fine, but either I missed the expectation-setting in the talk abstract or the abstract didn't include that info.

Venue-wise, the projection screen was 16:9 but slides were 4:3; not sure what aspect ratio the projector actually had. If it could do 16:9, that would've also provided enough slide width to make things a bit more legible.

Finally, Fairfax B with the specified seating setup was a bit of an eco chamber, but very much not the speaker's fault so no demerits for that.