../Bootstrapping software delivery
A short series of posts to bootstrap your software delivery.
Coming soon- Delivery team’s ways of working, Getting started with cross-functional requirements and, Running a live service.
🗓 Oct 22, 2023 📖 1 min
Often when setting up a new project/ programme/ product we forget to make our principles, constraints, and ways of working visible. There tends to be a group understanding however, churn happens and tribal knowledge dissipates. From no fault of any individual this can end in disaster and inevitably many difficult conversations.
🗓 Oct 27, 2023 📖 12 mins
Joining a new team is often painful and slow. Often you have to work out who to talk to, what software to install, request to be invited to meetings, hunt around for access to environments and repositories, and many more tasks. Without clear documentation, things will fall through the cracks giving vastly different onboarding experiences to new joiners. This post’s goal is to streamline your JML process, delivering value faster.
🗓 Nov 2, 2023 📖 12 mins
It is important that everyone in the team has a shared understanding of how they work together, however having the right level of documentation is tricky, especially around ways of working. Not enough will cause team members to not understand principles, boundaries or constraints which could impact mental health, and too much will overload team members, running the risk of key pieces of information being overlooked. Finding a balance is important and is an ongoing task and requires continual care.
🗓 Nov 3, 2023 📖 13 mins
Cross functional requirements (CFR’s) should be owned by the business. When setting up your software delivery capability this can be a hard ask. We have the best intentions to craft a set of well defined, testable cross functional requirements, however to do this we need to ask the organisation to become experts in maintainability, accessibility, resilience, security, privacy, reliability, compliance, disaster recovery to name just a few.