Your browser does not support JavaScript!

CASE STUDY

Painless Project Scoping with Juntoscope

The Problem

Determining a scope of hours for a large project that will be completed by a team of developers is difficult and leaves too high of a margin of error - and mistakes can be costly! Project Managers need a way to accurately determine the scope of a project in a way that accounts for differences in experience levels across a team.

The Goal

Create an app that allows a team to accurately scope a collaborative project in a way that is seamless, painless and reduces the margin of error. Our audience? Developers, project managers, consultants, and anyone looking to maximize the efficiency of their team.

juntoscope mobile view

The Product

The goal of JuntoScope is to help teams determine scopes for tasks in Teamwork.com © Projects more accurately, quickly, and efficiently to keep projects within budget and on time. Integrating with Teamwork Projects API, teams will be able to:

  • Scope tasks anonymously and accurately without influence of other team members
  • Determine team averages for scoped items to give the best estimate
  • Allow team members to scope items easily through their mobile device
  • Increase accuracy of scoped time for tasks within Teamwork Projects
  • Prevent teams from going over scope
  • Improve ROI
  • Decrease time spent scoping tasks

The Process

case study discovery icon

Discovery

  • Identify the problem
  • Research competing products
  • Create a lean canvas and feature pyramid
 
 
case study design icon

Design

  • Wireframing and user flows
  • Creation of branding and design guidelines
  • Implementation of guidelines
case study development icon

Development

  • Documentation, architecture & server set up
  • Creation of framework
  • Feature development & review
 
 
case study quality assurance icon

Quality Assurance

  • Feature Testing
  • Bug Fixes
  • Final review & app submission
 
case study deployment icon

Launch!

 

A Deeper Dive

Design

We began the design process by researching similar apps on the marketplace and identifying features we liked and did not like about them. We then set up user flows and wireframing each identified screen. This process, along with the design and styling phase, occurs in Sketch . After completing the full skeleton, we reviewed each user flow and tried to identify any gaps or weaknesses in the user flow. From there, we made modifications and began identifying styles and colors for the app. We created a logo and a splash screen and applied the styles to the rest of the screens. We then created a working prototype in Marvel to aid our development team in the next phase and prepared for handoff.

Development

We began the development process with a full design review. Our team worked closely with the designers to document a list of feature requirements that would later translate into development requirements. From there, we architected and established a base draft for client and server side implementation. We iterated through a review process as we gradually expanded and started to develop features.From our draft a skeleton client-side application is started in-tangent with developing server-side implementation to test and ensure all the data and state was expected and is functioning where it needs to be. Additional developers then followed in client-side to finalize pieces of the skeleton to reflect the designs. As each portion finished, it is formally reviewed, tested, and merged into a `master` branch for that app version. We reviewed these branches at critical milestones and had our quality assurance team review in order to ensure we stayed on top of bugs, in which we tracked in Github.

What we learned

Throughout the process of developing JuntoScope, our team learned the importance of establishing a process that is fully understood by each and every member. Our company was going through a transitional phase early on in the development of JuntoScope bringing on new team members and creating efficient processes. Towards the end of the session phase we discovered that the processes we established for work with our clients wasn't being diligently followed for JuntoScope.

This included designs that were not fully reviewed and understood by our development team, designs that did not follow guidelines with consistent styles and symbols, and a lack of forethought into the user experience of people not familiar with the app. What made sense to or team did not make sense to new users. This goes back to the saying, if your user interface needs to be explained, it's no good.

As our team came close to launching JuntoScope , we learned from Teamwork.com that they were changing the way their API worked and this forced us to go back to our design and development teams to work in the new authentication flows. This set our team back a few weeks from our initial planned launch. We learned the importance of staying up to date with technical updates to software that we integrate with so we immediately subscribed to their announcements.

Designing and developing JuntoScope was a great learning experience for our team as we used this as a time for us to perfect our internal processes that make all of our subsequent products seamless. This has had a lasting impact on the quality of apps that we produce for our clients and ultimately has made us a better team.