-
Writing the Engineering Strategy now. It looks obvious, boring, and opinionated. It's not anything the teams didn't know already. Putting it into a paper to help make faster decisions I explain what influenced the most in writing the engineering strategy here 👇Permalink On twitter.com
♻️ 2 Retweets ❤️ 4 Favorites Mood 0
-
The teams that had good documentation practices like 👉 Architectural-Decision Record 👉 Request For Comments 👉 Post-Mortems influenced the Engineering Strategy way more than the ones who didn't (and that information was easily accessible) Clear problems & solutions statementsPermalink On twitter.com
-
Surveys to understand current Engineering Pains are crucial to drive good strategy I did an async workshop to collect: 👉 Perception of @4keymetrics of Accelerate 👉 Engineering Experience Survey to assess cognitive load 👉 Sociotechnical Architecture 👉 Unfinished initiativesPermalink On twitter.com
-
@4keymetrics Asked each team about: 👉 Risks they see 👉 Concerns they have about the current situation 👉 Ideas they have to improve thatOn twitter.com
-
@4keymetrics The Engineering Strategy was quite easy after that. 👉 Aggregate info 👉 Syntethise that info that's repeating the most 👉 See if those points match the company OKRs 👉 Find the overlappings and present them That's the Engineering Strategy 🙌Permalink On twitter.com
-
For me, a good engineering strategy needs to be: 👉 Concrete 👉 Actionable 👉 Achievable if the best conditions are met Sometimes I confused Engineering Strategy with Vision. It implied to not be useful, way too generic, and not serving either as a strategy or long term.Permalink On twitter.com