Feature delivery and product planning on new and existing BBC products, inside an account team of around eight.

The BBC's work was held by an agency, which ran an account team of around eight across products already live and products still being built. We joined that team at senior engineer level.

The brief covered feature work and the planning that sits in front of it, so we were in product and engineering discussions as well as writing code. This page does not name the individual products.

Reach is the constraint. The audience for these products is in the tens of millions, which sets both the cost of a bad release and the size of the regression surface.

Eight people covering new build and existing products is the other half of it, because the same small group carries maintenance and new features. The technology on the engagement included Optimizely alongside Node.js, React, Redux and Jest. We cannot now separate which products were new from which were already running.

We held a key seat on that account team, delivering features on new and existing BBC products and contributing to product and engineering planning alongside that delivery.

The stack was Node.js on the server, React with Redux and React Context on the client, Jest for tests, Docker and Bash around the build, and GitHub with JIRA for the workflow.

Features shipped on BBC products reaching an audience in the tens of millions, from inside an account team of around eight.

We hold no release counts and no product performance figures for this engagement, and we are not naming the individual products. The audience and the team size are what we can evidence.