Due to the tight schedule we were working with, we adopted a "build, measure, learn" philosophy. We stripped the feature to its bare essentials, relentlessly seeking shortcuts and alternatives. Each iteration brought us closer to a viable solution, allowing us to refine our approach and prioritize risk mitigation continuously. This meant:

• Streamlining the design: Instead of a complex "build" layer, a simple 5% margin around the blueprint sufficed.
• Concentrating on web development: Mobile development was deferred to avoid spreading resources too thin.
• Utilizing lightweight data storage: JSON files replaced a full-fledged database for efficient data management.
• Delaying authentication: A login screen was deemed non-essential in the initial stages.

Our collaboration with the client began with a highly effective chartering session, an essential practice in the Industrial Logic toolkit. This initial day of focused alignment proved invaluable, fostering a shared understanding of the project vision and goals. With a crystal-clear understanding of priorities – validating costs, confirming feasibility, and creating a compelling demo – we were able to navigate complex decisions with ease and focus our efforts on delivering maximum value for the upcoming trade show.

"Working with Industrial Logic was a really collaborative and educational experience. It wasn’t just about building features—they worked with me to slice up the work in a way that made sense, and they always found ways to validate our underlying assumptions as we went along. It felt more like a true partnership rather than a client-developer relationship." Founder, Aurora Nexus

Our approach embraced an iterative development cycle, focusing on delivering a compelling product vision through carefully planned milestones. Each stage was meticulously crafted to showcase key features and validate core assumptions, while ruthlessly eliminating non-essential elements. This "less is more" philosophy allowed us to maximize impact with minimal resources, ensuring each milestone resonated with stakeholders and effectively conveyed the product's value proposition. This meant:

By the Numbers:

• Number of named releases: 4
• Number of features per release: 2, 8, 10, 4 (these last 4 were post trade show goals)
• Ratio of Stories to Discovery Trees: 3.2

Our agile approach, characterized by rapid iterations and frequent course correction, demanded a project-tracking system that could keep pace. Conventional tools like Jira, which we utilized to track larger items, proved cumbersome for capturing the nuances of our dynamic workflow. Instead, we adopted Discovery Trees, a lightweight and visually intuitive system. These "trees" provided a transparent, real-time snapshot of our progress despite the flurry of new information and decisions inherent in building better software sooner.

With 67 trees completed, averaging 6 tasks each (ranging from 1 to 46), and an average depth of 2.2 levels (ranging from 1 to 7), Discovery Trees effectively mapped our journey, ensuring transparency and focus throughout the project.

Our commitment to rapid iteration and continuous learning led us to adopt a "demo-driven" development approach. We created a direct feedback loop with stakeholders by showcasing new features in the live environment, allowing for early validation and course correction. This iterative process not only accelerated development but also challenged our assumptions. On multiple occasions, the client embraced functionalities initially perceived as flawed, highlighting the value of real-world testing and continuous feedback in shaping a successful product.

By the Numbers:

• Days to first demo: 3
• Average demos per week: 3
• Average commits per demo: 35

We prioritized early risk mitigation by establishing a "walking skeleton" – a minimal, end-to-end version of the application – within the first two days of development. This skeletal framework, complete with automated deployment to production, served as a foundation for continuous integration. With an average of 22 commits per day, we aggressively integrated new features and addressed potential issues in their infancy. This proactive approach allowed us to rapidly learn new technologies, mitigate integration risks, and prevent the accumulation of technical debt that could impede our progress.

By the Numbers:

• Total Days: 49
• Total commits: 1092
• Average commits / Day: 22
• Ratio of commits by Developer: 21 : 29