Pagico for Project Management
Since I have 2Do for handling tasks, I have Pagico for handling the project. The main difference is that Pagico handles the larger details. For example, you can define the overall pieces of a project, attach relevant requirements documents, add links to important sites, and set up contacts for people that own different parts of the project.
I find it very handy to connect all the major documents and milestones of a project within Pagico, then handle each of the individual parts (tasks and test plan) within 2Do.
For example, the Jira Epic is listed in Pagico, with the projected start and end date. I then add the requirements, the components under development, PDF documents, screenshots, links to sites or APIs, and any other documentation that I will need to keep track of. I can then make checklists, list milestones and review what needs to be done and when. This would come in the form of, on 7/1/2019, component X should be complete and deployed to QA.
This is a very good way to keep an overview of a project and when it’s due. I don’t need the hassle and bloat of a tool like Microsoft Project. But I do need more than documents and tickets scattered all over Jira and Confluence. I want them local to my machine and focused on what I need to accomplish.
I’ve tracked several projects this way and it’s very beneficial. I have a better idea of when to expect code components and when we need to move to the next phase. Plus, taking the time in the beginning to plan and collect project data, saves huge amounts of time overall.
This is another tool I found on sale on Stacksocial. It has also been included in Bundlehunt. It’s well worth the investment and I run copies at work and at home.