DevTracker

Showing summary, results, data, and an explanation of the results
Showing the labor statistics and what project inputs there are, as well as if more are needed
Dashboard showing all the projects and their feasibilities

Inspiration

We were all interested in building a project that could have real world applications, so learning about Innovate413 was very intriguing. We took inspiration from their 'Problem 2' prompt, planning our project around creating a user-friendly interface to organize and evaluate the complexity of tasks distributed among different teams.

What it does

Assigning appropriately complex tasks to all the individual members and teams in a company can be daunting, and that task gets even more overwhelming when it comes to keeping track of different deadlines and diverse project goals. With DevTracker, managing many groups becomes easy with a user-friendly interface that clearly shows the feasibility of a project and provides points for effectiveness improvement.

How we built it

We began with the backend, planning out the logic and then implementing it. We began by listing out the inputs we would expect and how they would be used to calculate complexity. We included an additional feature that factors in the experience of the team members when calculating the number of work hours the team could provide until the given deadline. With all this data, we were able to make data sets that could then be used for risk analysis. After we had basic versions of our formulas and API usage, we began working on the frontend, which was built with HTML, JavaScript, and CSS .

Challenges we ran into

Aside from integrating the API and learning how to use the complex language syntax, our biggest logic-based challenge was in making the complexity rating calculations. We had to carefully consider what factor could affect it and in what way, and how much weight each input factor should have on the ratings. From there, we had to decide how to do a risk analysis that could be linked directly to the data we calculated, and present possible solutions for non-feasible projects.

Accomplishments that we're proud of

We're proud of our ability to work parallel in backend and frontend through snags and the occasional API key issues. We're also proud of our extensive research and redesigning and adaptation of code functions and statistical analysis.

What we learned

Overall,

Integrating the Gemini API into a complex project with many different factors and moving parts
Solving real-world problems through small-step applications
Creating a working web app with given criteria and constraints in a very short period of time