Project Rundown
We are to create an 'add-on' for an upcoming software release for fieldGo, said addon will consist of a dashboard that connects to an API which will serve the desired statistics from the clients fieldGo database.
After studying with Patrick for some time I was well aware that he would prefer the front-end side of development whilst I prefer the back-end so that works out pretty well! He confirmed my suspicions and we agreed to split the work down the middle for now keeping in mind that he or I might need to help the other in the future.
The dashboard is to show the following statistics:
It was entirely up to us to come up with the design and present it to the team for approval which left us with a comfortable level of autonomy, we took to the whiteboard to sketch out our design then the legend Patrick sketched it up in a wireframing tool:
We are to create an 'add-on' for an upcoming software release for fieldGo, said addon will consist of a dashboard that connects to an API which will serve the desired statistics from the clients fieldGo database.
After studying with Patrick for some time I was well aware that he would prefer the front-end side of development whilst I prefer the back-end so that works out pretty well! He confirmed my suspicions and we agreed to split the work down the middle for now keeping in mind that he or I might need to help the other in the future.
The dashboard is to show the following statistics:
The project was surprisingly quite achievable which took a weight off our shoulders, we can focus on this MVP product before potentially expanding on it in the future.
It was entirely up to us to come up with the design and present it to the team for approval which left us with a comfortable level of autonomy, we took to the whiteboard to sketch out our design then the legend Patrick sketched it up in a wireframing tool:
Basic design as you can see but it allowed us to present our ideas in a way that would easily invite criticism, following some feedback from the team we locked the design in and moved ahead in our planning phase. Patrick was planning to research some different plugin options for displaying graphs our dashboard page, I was moving into planning the API before developing as advised by Chris.
To plan the API I did up an API specification document in which I documented what the API would take as parameters and what data it would return, this allowed me to make quick drafts and then hardness Chris's infinite wisdom to allow me to plan further ahead. After draft version 3 we felt comfortable with moving into development.
Our next task before moving in development was planning of our user stories, I went on to plan my backend tasks & Patrick took care of his. Going into next week we felt prepared and ready to go!
No comments:
Post a Comment