Sublime
An inspiration engine for ideas
the old system, the question is: Under which topic do I store this note? In the new system, the question is: In which context will I want to stumble upon it again?
Sönke Ahrens • How to Take Smart Notes: One Simple Technique to Boost Writing, Learning and Thinking – for Students, Academics and Nonfiction Book Writers
One of the most common challenges encountered in software development is the focus of teams, product managers, and organizations on managing cost rather than value. This typically manifests itself in undue effort spent on zero-value-add activities such as detailed upfront analysis, estimation, scope management, and backlog grooming. These symptoms
... See moreJoanne Molesky • Lean Enterprise: How High Performance Organizations Innovate at Scale
The developers set the budget for an iteration by measuring how much they got done in the previous iteration. The customer may select any number of stories for the iteration so long as the total of the estimate does not exceed that budget. Once an iteration has been started, the business agrees not to change the definition or priority of the
... See moreRobert C. Martin • Agile Principles, Patterns, and Practices in C# (Robert C. Martin Series)
Frameworks over Processes Less Is More The Hot Potato Process A Change in Tools Needs a Change in Behavior Hot Potato Gotchas Resistance to New Workflow Questions for Reflection
Dan Mall • Design That Scales
better/faster/cheaper.
Patrick Vernon • Venture Capital Strategy: How to Think Like a Venture Capitalist
1: Architect products; evolve from projects to products. Architecting products is more efficient than just designing point solutions to projects and focuses the team on its customers. Principle 2: Focus on quality attributes, not on functional requirements. Quality attribute requirements drive the architecture. Principle 3: Delay design decisions
... See moreMurat Erder • Continuous Architecture in Practice: Software Architecture in the Age of Agility and DevOps (Addison-Wesley Signature Series (Vernon))
A stream-aligned team aims to produce a steady flow of feature delivery. A stream-aligned team is quick to course correct based on feedback from the latest changes. A stream-aligned team uses an experimental approach to product evolution, expecting to constantly learn and adapt. A stream-aligned team has minimal (ideally zero) hand-offs of work to
... See moreMatthew Skelton, Manuel Pais • Team Topologies: Organizing Business and Technology Teams for Fast Flow
Releases are not cast in stone. The business can change the release content at any time. The business can cancel stories, write new stories, or change the priority of a story. However, the business should strive not to change an iteration.
Robert C. Martin • Agile Principles, Patterns, and Practices in C# (Robert C. Martin Series)
iv. Seu serviço ou produto é operacionalizado por meio de um produto mínimo viável.