Introduction
Every project you plan will be different. It will have different timelines, different objectives, and different tasks that will need to be completed. However, no matter what the project is, there is a checklist of items that you can run through during the planning process, that if you complete will make sure the project runs smoothly.
1. Define an MVP
An MVP is a Minimal Viable Product, and it essentially means the minimum amount of features you technically need to consider your project “ready for market”. This is a very important thing to define before you ever get started and is going to be the guiding light when breaking down your project into it’s various tasks. It is also very important that you put forth a decent amount of thought into this because once you establish what your MVP is, you aren’t supposed to change it. There is a common trap that many projects fall into, where there is always another feature to add, the timeline keeps getting extended, and project is ultimately never completed.
A well thought out MVP will set the stage for you to know exactly what needs to be built to consider the project finished.
2. Set Up a Project Board
Once you establish an MVP you need a place to break down the project into features and tasks, and for this you need a project board such as Lancer. These boards allow you to record everything that needs to be completed to satisfy you MVP requirements, and easily see the status of all of the different items.
Project boards allow for you to assign tasks to members, track their progress, add comments, add subtasks, and see overall stats of the project. They are absolutely essential for the successful development of a project.
3. Thoroughly Define Pages, Features and Tasks
Just like with an MVP it is critical that you break down the project into it’s actionable items. I have always found it is best to separate it out into both pages and features. This is because pages will have design elements that you won’t consider a feature, there will be times where there are multiple features on a page, and there will be features that are used across multiple pages.
It is completely up to you if you decide to create each page and feature as a epic or a task, but each should still have it’s own actional card that has
- the tasks or subtasks needed to mark it as completed
- any copy and visual resources that may be needed
- Estimated hours to complete
- A start and end date
You should create cards for every aspect of your projects MVP. You may need to adjust estimated time or start dates but you should add as much information as you can before you start any development because it will ensure that you stay on course.
4. Create UX/UI designs
As a developer this can be a tough one but is a very important step to complete if you can and will save you time in the long run. It is way easier to update a design in Figma than it is to update templates in your code. Additionally, a well flushed out UI designs ensures that the entire scope of the project is captured and is incredibly useful in establishing your MVP.
When it comes to development, visual references to projects, pages and features allow for accurate architecture, more thorough cards, and increases the likelihood that gaps are caught before development starts.
5. Estimate Hours and Timelines
When planning a project it may be hard to know exactly how long each task will take and where it all will fit in on a calendar. However, it is important that you at least get estimates for all of your cards. This will allow for you to at least have a baseline for how much work there is to be done and how it all falls on the calendar. For example, you may notice after initial planning that you have 4 major tasks assigned in a single month with 250 estimated hours. This may not be an achievable goal and gives you the opportunity to move items around to create a realistic time-board before development ever starts.
6. Get Feedback from Team Members
If you are working with a team it is important that you don’t plan your project in a silo. Nobody knows everything, and the most accurate project plans come from collaboration. It is very important that everyone is in agreement on what the MVP requirements are, timelines, and what tasks are assigned to them.
7. Continually Update Your Project Board
Once the initial planning is done and you are ready to start development, it is important that you keep your project board up to date. It is a living document and is only useful if you take care of it. When maintained properly it will provide valuable feedback about the project, what/who is struggling, what estimates were right and wrong, and provide the information you need to adjust in the right way. Additionally, a well maintained board will serve as a reference for future projects and estimates and each future development project should become easier to plan.