Difference between revisions of "Resource planning/en"

From 2value wiki 2
Jump to navigation Jump to search
Line 39: Line 39:
 
#Is the transaction between customer and supplier completely finalized?
 
#Is the transaction between customer and supplier completely finalized?
  
−
===Good resource planning double checks and allows for a royal buffer in time===
+
===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."
 
::Input: "The photo's can be found on the usual place on our web site. Just log in and you can download them."
 
::Answer:  
 
::Answer:  
Line 50: Line 50:
  
  
−
==Voorbeeld 2: site inpakken==
+
==Example 2: archiving/packaging a site==
−
  Als je een template moet ontwikkelen
+
  If you have to develop a template
  
−
===Goede resource planning dubbelcheckt en houdt een flinke buffer in tijd===
+
===Good resource planning double checks and allows for a royal time buffer===
−
::Input: "Als je nog even wacht, dan hebben we echt de laatste versie voor je, met alles erin!"
+
::Input: "If you can wait for a bit longer, we'll have the latest version for you, with everything in it!"
  
−
::Antwoord:  
+
::Answer:  
−
#OK, maar lever de huidige versie binnen de afgesproken tijd, vanmiddag 17u ''Als de zip-file groter is dan 20MB laadt hem dan op Dropbox. Hang het bestand of de Dropbox credentials hier aan de case <url>.''
+
#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>.''
−
#Kijk even de manier van exporteren van de site en database door in onze wiki. "Neem het tot u en handel ernaar", Zonder tegenbericht gaan we ervan uit dat je daaraan hebt kunnen commiteren of leg uit waarom het anders is.
+
#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.  
−
#Indien Dropbox: stuur shares voor de verwerker mee ''Bevestig even de eerste geslaagde login door de verwerker van de zip''
+
#In case of Dropbox: include share details for the user  ''Confirm the first successful login of the user of the zip-file.''
−
#Wanneer ben je voor de verwerker van de zip beschikbaar voor uitleg morgen ddd. <datum>? Het misschien niet nodig, maar je weet nooit.
+
#When are you available for the user of the zip file for explanation/questions: Tomorrow, <date> <time>. It might not be necessary, but you never know.  
−
#De site wordt door ons getest op <datum> maar wil je de case <url> in de gaten houden, we notifyen je ook, want het zou prettig zijn als je even bevestigt dat het goed zit.
+
#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.  
−
#Welke toegangssrechten zitten op de site? Zou je die rollen en logins willen plakken in de case <urls>
+
#Which access privileges does the site have? Could you paste those roles and logins in the case <url>.
  
−
===Slechte resource planning gaat uit van goed vertrouwen===
+
===Bad resource planning is based on good faith===
 
::Input: "Als je nog even wacht, dan hebben we echt de laatste versie voor je, met alles erin!"
 
::Input: "Als je nog even wacht, dan hebben we echt de laatste versie voor je, met alles erin!"
 
::Antwoord: "Super, dan hebben we ook de minste verschillen straks."
 
::Antwoord: "Super, dan hebben we ook de minste verschillen straks."

Revision as of 06:39, 6 July 2011

Language: Nederlands

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 satisfies the expectation of the processing party:

  1. Content
  2. Completeness
  3. Format
  4. Size
 A promise can usually be obtained, but the actual delivery ....

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?

If everybody that has to work on a task has the necessary resources.

Example 1: Photo gallery

If you want to make a gallery with photo's, 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 to work with them!"

What the receiver doesn't check:

  1. Where exactly are they located?
  2. Does the login work for the person using 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>
  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: "Als je nog even wacht, dan hebben we echt de laatste versie voor je, met alles erin!"
Antwoord: "Super, dan hebben we ook de minste verschillen straks."

Waar de ontvanger geen rekening mee houdt:

  1. Hoe klein de verschillen ook zijn: er zijn verschillen en dat betekent even veel werk als "grote verschillen"
  2. Hij verkleint de buffer voor de verwerker
Retrieved from "http://wiki.2value.nl/index.php?title=Resource_planning/en&oldid=4733"