As you know, deadlines are important and thus you need to ask for them or suggest them for every task you discuss. It’s the only way to ensure there is an agreement for delivery and you reduce you learning curve for common tasks to your project. You will have team members that consistently self assign,
You might be tempted to have a threshold for documentation, meaning “when they re-labeled that field for us from Customer to Client, no big deal” and skip noting this in your log but don’t skip it! Especially since everything is essentially a “version 1”, you need to have a log in case there is ever
This is a common happening, someone is unaware an application or process is being eliminated: I knew they were looking but I never got an email it was final I though instead of ABC we were going with XYZ Wasn’t that put off until next year? And so on. For a roll out, you need
Now that the application or system has been purchased and finalized, how to proceed? The next few posts will outline some considerations when rolling out a system, application, or process. One of the most important items is to review, once finalized, the contract: What is the vendor promising? What is the SLA service level agreement