In my previous post about this topic, I discussed how I could quickly build out an app that will bring your idea to life. I’ll discuss another approach in this post about “Proof-of-Concept” testing.
“Can what I have also do this?”
Often times a client of mine might have some bits and pieces of an app or project but they want to push what they have to the limits. Or the client is unable to grasp how a software acquisition works. So that’s when they call me up and say “Josh, take a month and figure out everything this can do. When you finish, report back on what you think and what might need to change in order to maximize its potential.”
First, I’ll take some time to fully understand the subject area. Are you looking to integrate IoT devices into an informative network? Then I’ll research IoT devices. Do you need to aggregate international phone call protocols across the world? Then I’ll spend some time researching how the world’s phone network is built. I firmly believe that in order to be the best at what you do, you need to understand how that thing works. For example, I’m running a computer camp for my son’s friends this summer. So, instead of diving right into code, we are spending one full day learning about computers and how they work. Once I have a good grasp of the topic area, I’ll start learning the mechanics of the program. How does it load data? What platform does it use? From there, I go and complete the project, documenting the issues and where the application excels.
In this scenario, as the project wraps up, I will submit full documentation about the work I performed. It can be a written report, a presentation, or both, and I am happy to come and present in person to the stakeholders in the project.
- Learn the subject area
- Understand the mechanics of the program
- Complete the project
- Submit a report with positives and negatives along with suggestions for future tracks of development
I’ll put together one more post about what benefits proof-of-concept testing brings to your projects.