Skip to content
#Management

Improving Software Flow • Randy Shoup • YOW! 2022 (Category Management)

#Management #Software #SoftwareArchitecture #Architecture #Processes #Leadership #Culture #Devops

Cool. speech Randy is about building software. Randy himself is a VP Engineering and Chief Architect at eBay, so he has a great mix of architectural and process recommendations. He built his speech on 5 book ideals The Unicorn Project (me told before)This is a sequel to a popular book. The Phoenix Project (About her, too. told earlier). These are the five ideals.

  • Locality and Simplicity This is about architecture and the following approaches are proposed: (modular services, orthogonal domain logic, event-driven architecture, immutable logs, embracing aynchrony). Interestingly, here is an analysis of the case from Walmart about their scenario of checking the availability of goods for shipment, where the synchronous chain of 20+ Services has been converted to asynchronous architecture and synchronous chain of just three services (The others worked out asynchronously). You can see this Walmart case separately. speech Devops of DOES19 Las Vegas Conference
  • Focus, Flow, and Joy - here we are talking about development processes, about kanban and WIP, as well as about the flow state, about the difference in the schedules of individual contributors and managers. By the way, there is a reference to the book “Visualize the work” (“Making Work Visible”)about wrote Medium.
  • Improvement of Daily Work This is about strategic programming. (Technical investment instead of technical debt)Continuous testing, test-driven development, continuous delivery, and the use of common currency (time, people, money) Evaluation and argumentation of technical investments (They will have to compete with product tasks that are valued in the same currency.) This will create an improvement budget.
  • Psychological Safety - This is about the project.Project AristotleIt was launched by Google to answer the question “What makes a team effective at Google?” And the answer, as you can see, was psychological safety. I recommend you to study in detail on page The project itself. Plus, the author talks about the culture of blameless postmortems, which I also talked about a few years ago in a report.Postmortems Culture or How We Learn w o i h fakapa"
  • Customer Focus We need to focus on customer outcomes, not output in the form of the results of our activities. Business outcomes require clear business metrics and clear customer metrics, and engineers need engineering discipline and business problem solving skills.

Overall, I enjoyed the talk and recommend it to tech leaders who want to improve their development processes and their systems architecture.

#Software #SoftwareArchitecture #Architecture #Processes #Management #Leadership #Culture #Devops