Customer Obsessed Engineering
Subscribe
Sign in
Home
Notes
The Delivery Playbook
Archive
Leaderboard
About
The Delivery Playbook
Latest
Top
Discussions
2.9 Functional architecture
Your functional architecture assembles a finished design. It answers the question, “exactly how will we build our product?”
Nov 19
•
Zac Beckman
Share this post
Customer Obsessed Engineering
2.9 Functional architecture
Copy link
Facebook
Email
Notes
More
3.0 Delivery (phase 3)
Phase 3: Creating detailed technical specifications, engineering work, and building a product increment that is ready for production.
Nov 19
•
Zac Beckman
Share this post
Customer Obsessed Engineering
3.0 Delivery (phase 3)
Copy link
Facebook
Email
Notes
More
2.8 Delivery processes & tools
Your delivery toolchain impacts the entire team, every single day. Getting it right means massive productivity gain.
Oct 12
•
Zac Beckman
Share this post
Customer Obsessed Engineering
2.8 Delivery processes & tools
Copy link
Facebook
Email
Notes
More
2.7 Architecture foundation
Your architecture foundation should be immutable. It’s the bedrock on which everything is built, enabling your team to create new capabilities while…
Sep 9
•
Zac Beckman
Share this post
Customer Obsessed Engineering
2.7 Architecture foundation
Copy link
Facebook
Email
Notes
More
The 30-minute guide to Domain Driven Design: A secret weapon to solve tough problems (Part 2)
Create better team alignment, clearly define boundaries, and design around resiliency, scalability, and customer-driven value.
Aug 5
•
Zac Beckman
Share this post
Customer Obsessed Engineering
The 30-minute guide to Domain Driven Design: A secret weapon to solve tough problems (Part 2)
Copy link
Facebook
Email
Notes
More
2.6 Target state architecture
Methodically approaching your conceptual model of the future and the technologies that fulfill that future is crucial if you want to achieve or surpass…
Jul 29
•
Zac Beckman
1
Share this post
Customer Obsessed Engineering
2.6 Target state architecture
Copy link
Facebook
Email
Notes
More
The 30-minute guide to Domain Driven Design: A secret weapon to solve tough problems
Using domain driven design fixes your customer perception problems, aligns technology with business, and defends against complexity.
Jul 21
•
Zac Beckman
5
Share this post
Customer Obsessed Engineering
The 30-minute guide to Domain Driven Design: A secret weapon to solve tough problems
Copy link
Facebook
Email
Notes
More
2.5 Context mapping
Context mapping is all about avoiding entanglement: Creating greater efficiency with smaller, more capable components, better APIs, purpose-built data…
Jun 28
•
Zac Beckman
Share this post
Customer Obsessed Engineering
2.5 Context mapping
Copy link
Facebook
Email
Notes
More
2.4 Domain modeling
Domain modeling creates the foundation for your product architecture. It ensures your design is carefully crafted, fits the business purpose, and drives…
Jun 16
•
Zac Beckman
Share this post
Customer Obsessed Engineering
2.4 Domain modeling
Copy link
Facebook
Email
Notes
More
2.3 Strategic event storming
Adopt a design approach that focuses on your customer and isn't mired in the past. This means understanding the ideal product, documenting it in ways…
May 12
•
Zac Beckman
1
Share this post
Customer Obsessed Engineering
2.3 Strategic event storming
Copy link
Facebook
Email
Notes
More
2.2 Roadmaps and OKRs
We have to empirically measure progress toward success. "Features delivered" is old hat. Create customer-facing value every single time by knowing what…
Apr 15
•
Zac Beckman
1
Share this post
Customer Obsessed Engineering
2.2 Roadmaps and OKRs
Copy link
Facebook
Email
Notes
More
2.0 Blueprinting (phase 2)
Phase 2: Establish your product strategy, decide on your roadmap to delivery, and develop your blueprints and technical designs.
Mar 24
•
Zac Beckman
Share this post
Customer Obsessed Engineering
2.0 Blueprinting (phase 2)
Copy link
Facebook
Email
Notes
More
Share
Copy link
Facebook
Email
Notes
More
Error
This site requires JavaScript to run correctly. Please
turn on JavaScript
or unblock scripts