Building on our experiences over the years we’ve developed a list of key tasks required to complete prior to developers writing a single line of code. We hope these tips will save you some time on your next project.
1. Review everything
When it comes to any project its important to review all the material that your sales team and project manager are handing you. Make sure you take the time to sit in a quiet area and read through all of the material making notes as you go.
2. Ask Questions
Following up on the first task its very important to ask lots of questions. Even if the answers to every question is a simple yes, never underestimate the importance of asking questions and clarifying your understanding of functionality.
3. Review proposed technology
Anytime someone makes a decision to use a specific technology to solve a problem its always useful to review the technology proposed and ensure there are no missed opportunities. More often then not the person who is recommended the technology is doing so on tried and true past project successes. This however does not mean that new cutting edge technology wouldn’t be a better fit.
4. Talk with your development team
Even if you deployed every piece of functionality on previous projects it’s important to talk through what your going to be doing at a high level with your development team. It’s especially important to discuss functionality you’ve never deployed such as a twitter feed or other new technology solutions. Someone more often then not has a good idea to save you time, or recently solved a very time consuming problem with one of the technologies you’ll be deploying.
5. Plan your attack
Take the time to sit in a quiet area, think about how you’ll be developing this solution and then write it down! We can’t stress this enough as to how important it is to document what will be done first, second and so on. On top of that it’s important to have this information available to your project manager, after all he’s going to want reassurance you can hit and deliver on the clients time lines. Try using a gantt chart to create your plan as this is a simple yet effective way to dip your toes into this process.
6. Review your plan
Remember that even if you’ve spent two hours or six hours planning out what you’ll be developing first and second and what you’ll be developing last it’s important to review this with the project manager. They’ll be able to provide necessary feedback on concerns about client expectations and potentially bottlenecks you may not have considered.
7. Comp out functionality
At this point you should already have a design for your application however this design won’t illustrate every piece of functionality, and it’s not important to illustrate how a simple page will look before you get started. Any functionality that isn’t 100% cut and dry should be laid out. You can do this by hand, with many free layout tools or simply work with a designer to create rough composites that you can show to the client for sign-off.
8. Review everything with a team member
Take the time to review your plan and comps with another developer. It’s always easier to have a mistake or suggestion pointed out to you know before your 50% down the project. Have the other developer review your plan, your comps and talk him through everything so he understands what’s going to be developed without reading all of the information for the entire project.
9. Use pseudocode
Unless you’re the only developer in the world that doesn’t make mistakes or logic errors then this step is essentially for success. Layout your functionality in pseudocode being as detailed as possible. Overtime you’ll learn where details need to be very specific and where they can be a little less detailed. This process will help you stop logic problems within your code every single time.
10. Start coding!
By putting some planning upfront you’ve just saved yourself lots pain and suffering moving forward.
Good luck – we hope this will save you some time and ensure things move smoothly for you on your next development project. Please share any tips you have for improving the development process in the comments.
David Millar,
Lead Developer
Millar, as he is known around the office, is a rock-solid, workhorse coder. If anyone really understands what a chunk of code is doing it’s him. Family, friends, sports, and his wife are the most important things in life to him. He plays sports weekly and golf in the summer when he’s not busy hanging out with friends and family. Recently he got married to his wife Kate in a beautiful ceremony surrounded by friends and family on a perfect summer day. A humanitarian at heart, his positive demeanour is rattled most when “society makes decisions without considering more relevant information from the present”, and people “make self indulgent decisions that hurt society and everyone else”.