Once you have a mock up image of your application, you have a road map for how you want to get to a final product. However, this map doesn't really have a specific route to take and developers may choose different paths. Obviously, like a road trip, you can't just magically warp to the finish line. However, if you could get to California from New York by a more northern route or a more southern route. That's not to say one way is better than another, they're just two different ways to travel.So once we had our mock-up, we break up the team into jobs to insure that we each have different tasks that line up on some sort of schedule to help us reach our final goal. These jobs can vary from project to project depending on what exactly we need to get done. Here's a bit of insight into how we're breaking down responsibilities for How to Analyze Information.
- Mike is working on the actual coding for the application. He's getting the engine up and running and then building the code components you will use when you download the application.
- Jeff has been working on the various art we need. While this is an eReader and mostly text, we still need icons and art for the App Store. He's also working on design and text formatting.
- I've worked with app design, some text formatting, and along side Mike in trying to solve some problems we've had with code thus far.
While we each have specific jobs in the process, we tend to work hand in hand a lot. For instance, Mike may find a problem with the application and then all three of us will scour the internet looking for a solution to the problem, find a potential solution, and then go back to our individual projects.
While it seems simple, it's important to discuss plans of attack for each application so that all team members can stay busy and working towards a common goal.
While it seems simple, it's important to discuss plans of attack for each application so that all team members can stay busy and working towards a common goal.