​Microsoft Ignite has ended and that means some great new functionality and innovation are on the way!  As we scoured through the Ignite conference announcements and scheduled upcoming feature updates there were a couple of items we thought warranted being highlighted for a closer look.

​As much as we all wish it were otherwise, project requirements are not static. In fact, it’s rare when a project’s requirements don’t change. New technologies being released, changes in business goals or discovering some requirements weren’t captured during the initial project stages. These can all cause your project’s requirements to change.

1. Provide just in time learning

• ​Adopting a new tool or process in a few months?  Now is the time to start planning - but not yet time to start training end users.  Timing can be tricky, but ideally, it’s early enough to prevent user errors and late enough that employees can go back to their desks and try it out for themselves.