Sublime
An inspiration engine for ideas
Truly scaled Scrum is Scrum scaled.
Bas Vodde • Large-Scale Scrum: More with LeSS (Addison-Wesley Signature Series (Cohn))
Making the shift to working in terms of Intermediate Packets unlocks several very powerful benefits.
Tiago Forte • Building a Second Brain: A Proven Method to Organize Your Digital Life and Unlock Your Creative Potential
uma nova forma de organizar os esforços humanos.
Jeff Sutherland • SCRUM: A arte de fazer o dobro do trabalho na metade do tempo (Portuguese Edition)
Alternatively, lose the notion of projects entirely and build incremental capabilities in a steady flow.
Mark Schwartz • War and Peace and IT: Business Leadership, Technology, and Success in the Digital Age
Don't try to make it complete from the start. Refine it iteratively as you deliver. Treat deliverables as options, don't take it for granted that everything listed here will actually be delivered.
Gojko Adzic • Impact Mapping: Making a big impact with software products and projects
It is usually best to try to align software boundaries with the different business domain areas. A
Matthew Skelton, Manuel Pais • Team Topologies: Organizing Business and Technology Teams for Fast Flow
The First Way enables fast left-to-right flow of work from Development to Operations to the customer. In order to maximize flow, we need to make work visible, reduce our batch sizes and intervals of work, build in quality by preventing defects from being passed to downstream work centers, and constantly optimize for the global goals.
Jez Humble • The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations
The manifesto led with these four main tenets: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
Dan Mall • Design That Scales
Generally speaking, teams composed only of people with a single functional expertise should be avoided if we want to deliver software rapidly and safely. Traditionally,