About tracer bullet development
First defined by Andy Hunt and and David Thomas (1) in 1999, Tracer Bullet development describes an approach of getting the main functionality of a program implemented as fast as possible to a) collect feedback and b) see if this thing works after all.
In recent years this approach gained more popularity as it was taken up by the team around GROWS Method (2). The idea behind this approach is simple: “A working prototype is worth more than a thousand concepts.” It has become a common practice to create paper-prototypes or wireframes for visual interfaces to break down complex logic into more easy to understand visuals. The same applies to tracer bullet development. The critical piece in a piece of innovation is implemented without too much regards to compatibility of existing systems, legacy support or anything the like. As soon as this rough “code sketch” solves the core-problem, it can be tested against existing system, users, etc.
Especially in early-stage projects where complex technology is involved, it is definitely worth to think about not just visual mockups but also “technology mockups” in form of tracer bullet development to explore technical feasibility early in the project.
Build. Learn. Iterate.
Sources: 1) The Pragmatic Programmer: From Journeyman to Master (1999) 2) The GROWS Method (2014)