When I was looking for some e-book editions of classic texts, I discovered Standard EBooks https://standardebooks.org/
Especially if you're using a Kindle, the quality is so much better than if you download .mobi files from Gutenberg. It is an ancient format that doesn't provide good support for high quality text.
Read their Kindle FAQ for more details https://standardebooks.org/help/how-to-use-our-ebooks#kindle-faq
The #Lightweight emphasis on delivering frequently comes from an era when delivering every 6-18 months was commonplace and customers were starved for new features. Many of us don't live there any more.
Delivering frequently doesn't mean "Always Be Shipping New Features". It means practising delivery until you can do it in your sleep.
This is one way to generate options in order to enable a strategy that fits your business.
Co-creating (pair/mob programming) is even more important in remote working times.
The emergent behavior (going for lunch together, chats near the water cooler, spending time in the shared physical space, etc.) that was helping gel the team is gone now. Trust and vulnerability probably with it, as well.
Communication and interactions have become a lot more bounded and transactional.
Creating together is not an option, but became a necessity in sustaining a healthy, productive environment.
I've worked in the software industry for 22 years. Every single team/role structure that I've seen, I've seen fail. There are also successes. But anything *can* fail.
I am starting to think that one surefire way to guarantee eventual failure is to assume that team structure, roles, and responsibilities can or should be independent of the specific people in the roles. Or that roles and structure shouldn't evolve in response to the people in specific roles at the time.
Steve Wart
Allen Holub
J. B. Rainsberger (he)
Dragan Stepanović
Chris Ammerman