Resource planning/en

Language:	Nederlands  • English

What is Resource planning?

Ensuring that the input of customers and third parties is ready for use in a project or support. Refer to Zwakste schakel.

Why Resource planning

Actually getting the things available that have been promised is a huge challence, let alone aligning what the requesting party and the provider of the resource mean. Also that the resource meets the expectation of the processing party (user):

1. Content
2. Completeness
3. Format
4. Size

Who does the Resource planning

2Value's project manager.

How is Resource planning delivered to you?

1. Initially as written agreements via e-mail, but as soon as the project starts:
2. As cases in the customer group in the Service tool

What makes Resource planning good?

Everybody working on a task has the necessary resources.

Example 1: Photo gallery

If you want to make a photo gallery, these photo's must be ready and waiting for you.  

Bad resource planning is based on good faith

Input: "The photo's can be found on the usual place on our web site. Just log in and you can download them."

Answer: "Thanks, we'll get working on them!"

What the receiver doesn't check:

1. Where exactly are they located?
2. Does the login work for the person working with the photo's?
3. Which size do the photo's have?
4. Are the photo's optimized for use on the web?
5. Which property rights do these photo's have?
6. Is the transaction between customer and supplier completely finalized?

Good resource planning double checks and allows for a royal time buffer

Input: "The photo's can be found on the usual place on our web site. Just log in and you can download them."

Answer:

1. Where exactly are they located? Send a URL please.
2. Does the login work for the person using the photo's? Confirm the first successful login of the person using the photo's please.
3. Which size do the photo's have? We agreed on 200x300 pixels; the file name fits this structure and the edges have been rounded. Could you confirm in this case <url> that this is indeed the case.
4. Are the photo's optimized for use on the web? Can you upload the approvals of the marketing department and technical review in the case <url>.
5. Which property rights do these photo's have? Confirm the delivery under purchasing conditions of the customer in case <url>.
6. Is the transaction between customer and supplier completely finalized? Can you enclose upon delivery an overview of any outstanding obligations of the purchaser of the photo's.

Example 2: archiving/packaging a site

If you have to develop a template

Good resource planning double checks and allows for a royal time buffer

Input: "If you can wait for a bit longer, we'll have the latest version for you, with everything in it!"

Answer:

1. OK, but deliver the current version within the agreed time frame, this afternoon before 5 PM. Upload the zip-file to Dropbox if it's bigger than 20MB. Attach the file of the Dropbox credentials to the case <url>.
2. Read how a site and database is exported in our Wiki. Unless you notify us otherwise, we assume that you can commit to this or explain us why it's different.
3. In case of Dropbox: include share details for the user Confirm the first successful login of the user of the zip-file.
4. When are you available for the user of the zip file for explanation/questions: Tomorrow, <date> . It might not be necessary, but you never know.
5. The site will be tested by us on <date>, but also keep an eye on the case <url> (we will also notify you) because it would be nice to know everything works.
6. Which access privileges does the site have? Could you paste those roles and logins in the case <url>.

Bad resource planning is based on good faith

Input: "If you can wait for a bit longer, we'll have the latest version for you, with everything in it!"

Answer: "Great, than we'll only have minor changes to make later on."

The recipient doesn't bear in mind that:

1. It doesn't matter how little those changes are: fact is that there will be changes and they will be as much work as "big changes".
2. He decreases the buffer for the user.