Oct 25, 2020
The Software Process and Measurement Cast 622 features my interview with Brian Gill, CEO at Gillware. Brian is a serial entrepreneur in the software and cyber world. We discussed the importance of cybersecurity, real backups, having disaster recovery plans, and the fact that just having data in the cloud is not a security strategy.
Brian is a computer scientist, entrepreneur, and angel investor. Brian currently serves as Chairman of Gillware, which provides cyber risk assessments, data recovery, incident response, and digital forensics services. He is a co-founder of Phoenix Nuclear Labs and served on PNL’s board from inception to when it decided to spin-off SHINE Medical Technologies. Those two companies have raised over 100 million dollars of venture capital and employ hundreds of people in Wisconsin.
Re-Read Saturday News
This week we tackle Chapter 19 of Steve Tendon and Daniel Doiron’s Tame your Work Flow. Chapter 19 combines many of the moving parts from the previous chapters into a set of tools for monitoring the execution of work. The authors pick up at the portfolio level developed in Chapter 18. Portfolio items, once committed and placed into flow, can contain many groups of work that Steve and Daniel term Minimal Outcome-Value Effort or MOVEs (see week 14). Once in flow (being worked on), a flow manager picks up managing the MOVEs.
The Software Process and Measurement Cast is a proud sponsor of the following event!
Agile Online Summit 2020
The Agile Online Summit was created for people who couldn’t attend major conferences. This will be its third year, and the main goal is to bring major level agile speakers to people all over the world as well as spotlight some up and coming agile coaches and trainers. October 26th to 30th, 2020, Live and recorded too. https://bit.ly/3gNR2Bw
The Software Process and Measurement Cast 623 will feature my interview with Christian Clausen, author of Five Lines of Code from Manning Publications. We discussed why refactoring is needed, and the rules Christian has developed to get the most value out of refactoring. It's not like you are not spending time refactoring already . . . right?