The following will be a regular feature where we share articles, podcasts, and webinars of interest from the web.
Steve Pereira posted an experience report on Value Stream Mapping from his involvement with 3 different organizations over the past year. A value stream is the sequence of activities an organization undertakes to deliver on a customer request. The sequence is displayed visually to depict information and material flow. This is a great example of three different mapping exercises and the value provided through value stream mapping (VSM).
As a follow-up on the post above, VSM DevCon recently hosted a virtual conference on value streams. They posted all the recorded videos from the event (free to view). Details below: “As software development, delivery and performance become more complex due to modern architectures, value streams can help organizations unlock the bottlenecks and eliminate process waste to continuously improve how they work and deliver better experiences to their customers. Value stream management concepts are critical when the product changes frequently due to opportunities in the markets, the materials change due to the complexity of modern software architectures and means of delivery, and the output is often changing based on customer demands and expectations.”
Eran Kinsbruner examines several of the most popular testing frameworks used for webapp testing. He compares Cypress to Selenium to Puppeteer to the recently released Microsoft Playwright. Overall Selenium is the most flexible to use but does require more programming knowledge than the other three.
This article offers five ways to help manage technical debt within a team or an organization. In the post, the author recommends a team look to reframe software development strategy (new code standards, TD tracking, agile approach that promotes TD removal), integrate metrics into development (code coverage for unit tests, bug counts, etc.), test more frequently within a release cycle, maintain a knowledge base for standards & practices, and conduct regular refactoring sessions.