We’ve started testing phase 1 of AceProject 4.7 last week. So far, we’re really impressed with Pascal’s work. Not only is the software working as expected, but there are very few bugs to fix.
Phase 1 was mostly focused on improving task dependencies. Most AceProject users will tell you task dependencies are very rigid in AceProject. We use only hard logic: the predecessor task must be completed before its successor can start. Dates are mandatory. It makes it difficult to use task dependencies efficiently in the current system.
In AceProject 4.7, we introduce non-mandatory task dependencies. For dependency chains that can accept flexibility and overlap between tasks, you’ll be able to start a task even if its predecessor is not completed.
Even better: if your task doesn’t have dates or has incompatible dates with the predecessor, AceProject will propose some dates to you in a pop-up, so you don’t need to remember when the previous task ended.
We are getting ready to start working on phase 2 of AceProject 4.7. This phase will include improvements to the user workload report, and a new dashboard feature! I can’t wait to show you what it looks like.