Foundations of Sustainable Software

Creating effective software requires planning, insight, architecture, and cross-discipline collaboration. Ryan Cromwell will demonstrate strategies for maintaining a shared software solutions vision and techniques for guiding its evolution in a safe, sustainable manner.

Transcript

1. Ryan Cromwell SUSTAINABLE SOFTWARE
2. For makers, there is no better feeling than seeing something you've made being used.
3. Sustainable Development ‣ Having confidence in your efforts ‣ Feeling in control of the process ‣ Can do it consistently over time
4. We'll know more tomorrow than we do today. ~ Sparkbox, every day
5. How do you balance? Learning Confident Control Consistency
6. Confident Control Consistency Learning
7. https://seesparkbox.com/foundry/how_we_do_discovery Sparkbox Discovery ‣ Research ‣ Strategy Meeting ‣ Project Brief ‣ Technical Strategy ‣ Design & UX Strategy
8. Continuous Discovery Planning Build
9. Continuous Discovery Planning Build & Technical
10. A Tech Lead is... ‣ right hand to the project manager ‣ measured by the success of the team ‣ regularly describing the technical vision ‣ model of "how we work together" ‣ empowering and unlocking the team through communication, leadership, technical skill, and impact
11. A Tech Lead is... ‣ right hand to the project manager ‣ measured by the success of the team ‣ regularly describing the technical vision ‣ model of "how we work together" ‣ empowering and unlocking the team through communication, leadership, technical skill, and impact
12. Tech Lead: Sustainable Software ‣ Shared Technical Vision ‣ Planning ‣ Building ‣ Feedback system ‣ Evolving architecture
13. www.seesparkbox.com HAVE A TECHNICAL VISION
14. Technical Vision: High-level Architecture
15. Technical Vision: High-level Architecture
16. Technical Vision: High-level Architecture
17. Technical Vision: Integration Considerations
18. Technical Vision: Integration Considerations
19. Technical Vision: Diagrams
20. A technical vision enables decision making.
21. www.seesparkbox.com PLANNING
23. Pre-work ‣ Next stage vision ‣ Scenarios ‣ Diagrammed next step of the architecture ‣ “Decomps” ‣ Others: Wireframes, Designs, etc
24. Planning & Building: Next Stage Vision
25. Planning & Building: Next Stage Vision
26. Planning & Building: Next Stage Vision
27. Planning & Building: Next Stage Vision
28. Planning & Building: "Decomps"
29. Planning & Building: "Decomps"
31. Productive Planning ‣ Walk through the plan ‣ Create or review cards together ‣ Discuss questions ‣ Clarify understanding
32. Consistent, thoughtful planning provides confidence and enables decision making.
33. www.seesparkbox.com BUILDING
35. Building Confidence Confidence ‣ Validate assumptions ‣ Integrating often ‣ Test suite ‣ Deploying frequently
36. A great build and deployment pipeline encourages collaboration and transparency. https://seesparkbox.com/foundry/successful_software_build_and_deployment_pipelines
37. Engineer for speed & confidence ‣ Keep "master" deployable ‣ Small evolutions ‣ Fixture feature flags ‣ Unpublished urls ‣ Creating architecture seams https://seesparkbox.com/foundry/sustainable_software_decoupling_delivery_and_release_for_continuous_integration
38. Build with Confidence ‣ Clear, shared vision ‣ Robust build & deploy pipeline ‣ Technical Skill
39. www.seesparkbox.com FEEDBACK
40. Value Stream Metrics
41. Operational Health
42. Operational Health
43. Architecture Health
44. Architecture Health Unchanging Infrastructure
45. Architecture Health Simple, Safe to change
46. Architecture Health Danger Zone
47. Learning through feedback ‣ Operational insights ‣ Architecture insights ‣ Value stream metrics
48. Sustainable Software ‣ Thoughtful, continuous planning ‣ Robust build & deploy pipeline ‣ Solid engineering practices ‣ Great communication
49. Ryan Cromwell THANK YOU!