Astory: Build Software In Real Time

When we think about where software engineers spend most of their time developing projects, we typically think of a scrum board. The board contains tickets based on a pre-existing software architecture diagram, whether it is abstract or solidified. This diagram of the system ultimately serves as the source of truth for an engineering team's end goal. The tickets’ content represents what changes are needed to best capture the desired infrastructure.

However, these tickets contain discrepancies due to constantly changing system requirements. The discrepancies, on what needs to be built for a system versus what is developed, are exacerbated by the inability to communicate changes to the system across team members.

The standard routine for a software engineer, who’s working on building a system during a sprint, is to capture rolling changes in backlogged tickets, update the system a design document, and communicate the changes required with the team.

Frequently engineers forget the latter two steps and use the scrum backlog as a glorified todo list. The latter of the tasks are disruptive, and often viewed as tangential, to the main task at hand which is to write code.

These backlogged tickets are revisited in a refinement meeting in order to provide more details the team needs to select the ticket for development.

Every engineer on the team spends an exorbitant amount of time attempting abductive strategies to gather what requirements need to be addressed, and how to write the code to support those requirements.

Foreseeably this process can create a lot of slack in the software development cycle.

Astory aims to solve issues regarding, an updated model of what needs to be built, managing where the content on how to built a system is stored, and provides a live view of what the current system looks like.

Astory’s goal is to reinvent the process of building software to start with the design first. A team using Astory will first design the system; The design will parse their design into scrum tasks. These tasks can be exported to a team’s preferred scrum provider. In addition, teams can update their system diagram and Astory will conduct a comparison between which new tasks are required and re-serialize the diagram.

Check it out at:
https://www.astory.dev

Let me know what you think in the comments!