In a current project a lot of prototyping happens. This produces a lot of source code which I like to remove.

At the same time I would like to be able to access this code at a later date, For explaining why things have been done a certain way or reuse in other projects.

I also want to stay light on tools, so I'm looking for processes and templates that I can use to store this information.

I'm storing my source code in git.

3 Answers 3


Just store it in git, in a separate location. You're not likely to have capacity issues because of source code required for prototyping.

But you do want to exclude it from statistics as it may not confirm to strict coding standards.

  • Requests for additional information should be posted as a comment on the question, not as an answer.
    – Sarov
    Jan 9, 2017 at 3:36
  • @Sarov Removed from answer. jdog, I presume that if you would have asked your dev team that they would have answered the same. It's a bit strange that you rely on PM.SE instead of your team for this. Jan 11, 2017 at 12:58
  • I don't have a Dev team
    – jdog
    Jan 11, 2017 at 17:40
  • Ah, OK, I just assumed this because this is PM.SE. But yeah, you can also do PM without a team I guess... Jan 11, 2017 at 21:45

It's code, so use source control.

I would hope that source control is being used regardless of whether it is a prototype or not. Personally I'd recommend using source control even for "proof of concept" and other quick test projects to figure out how to use or do something.

As source control software is essentially an archive with version control, archiving your prototypes then simply becomes a matter of organization within the source control software that you use.

Depending on the source control software, you could use a separate repository, a separate solution / project group, a separate folder, or any combination of these.

  • Thanks for your answer. I realised that my question was vague and I didn't make clear that git is used from the start and the "prototypes" are not so much planned as such, but it is a rapidly changing requirements environment. Follow up question here: pm.stackexchange.com/q/20810/747
    – jdog
    Jan 10, 2017 at 17:38

One option is to use git's branching functionality. When you run one of these prototypes, do it in a branch (like a topic branch). For most of these, they would then just sit in their own little branches, separate from the main/development branch.

If you decide to keep and integrate the prototype code into the production code, all you need to do then is to merge the topic branch into the main/development branch.

  • Thanks. My question was a bit vague. Protoypes are not so much considered as such when created, but requirements change rapidly. Follow up question here: pm.stackexchange.com/q/20810/747
    – jdog
    Jan 10, 2017 at 17:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.