Difference between revisions of "Resource planning/en"

From 2value wiki 2
Jump to navigation Jump to search
(Created page with "{{Image|name=resource256px|width=256px|pad=20px|ilink=File:resource256px.png|float=right}} =Wat is Resource planning?= Zorgen dat input van klanten en derden klaar staat voor ver...")
 
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
[[Category:Method]]
 +
{{Languages|Resource planning}}
 
{{Image|name=resource256px|width=256px|pad=20px|ilink=File:resource256px.png|float=right}}
 
{{Image|name=resource256px|width=256px|pad=20px|ilink=File:resource256px.png|float=right}}
−
=Wat is Resource planning?=
+
=What is Resource planning?=
−
Zorgen dat input van klanten en derden klaar staat voor verwerking in project of support. Zie verder [[Zwakste schakel]].
+
Ensuring that the input of customers and third parties is ready for use in a project or support. Refer to [[Zwakste schakel]].
  
−
{{Languages}}
+
=Why Resource planning=
−
=Waarom 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):
−
Het daadwerkelijk beschikbaar krijgen spullen die zijn toegezegd is '''een grote uitdaging''', laat staan constateren dat vrager en aanbieder van de resource hetzelfde bedoelen. En dat de resource voldoet aan wat de verwerker had verwacht te krijgen:
+
#Content
−
#Inhoudelijk
+
#Completeness
−
#Volledigheid
+
#Format
−
#Formaat
+
#Size
−
#Omvang
 
  
−
{{Ambox|text=Toezeggingen krijg je vaak wel, maar de daadwerkelijk levering....}}
+
{{Ambox|text=A promise can usually be obtained, but the actual delivery ....}}
  
−
=Wie doet de Resource planning=
+
=Who does the Resource planning=
−
2Value's [[projectmanager]].
+
2Value's [[project manager]].
  
−
=Hoe komt Resource planning tot je?=
+
=How is Resource planning delivered to you?=
−
#Eerst als '''afspraken in tekst''' in de mail, maar zodra het project start:
+
#Initially as '''written agreements''' via e-mail, but as soon as the project starts:
−
#Als '''cases''' in de klantgroup in de [[Servicetool]]
+
#As '''cases''' in the customer group in the [[Service tool]]
  
−
=Wat maakt Resource planning goed?=
+
=What makes Resource planning good?=
−
Als iedereen die een [[PCON|taak]] moet uitvoeren de noodzakelijke resources heeft.
+
Everybody working on a [[PCON|task]] has the necessary resources.  
  
−
==Voorbeeld 1: Foto galerij==
+
==Example 1: Photo gallery==
−
  Als je een galerij met foto's wilt maken, moeten de foto's klaar staan.  
+
  If you want to make a photo gallery, these photo's must be ready and waiting for you.
  
−
===Slechte resource planning gaat uit van goed vertrouwen===
+
===Bad resource planning is based on good faith===
−
::Input: "De foto's zijn klaar gezet op de bekende plek op onze website, als je inlogt dan kun je ze downloaden"
+
::Input: "The photo's can be found on the usual place on our web site. Just log in and you can download them."
−
::Antwoord: "Dank je wel! We gaan ermee aan de slag!"
+
::Answer: "Thanks, we'll get working on them!"
  
−
Wat de ontvanger niet controleert:
+
What the receiver doesn't check:
−
#Waar precies staan ze?
+
#Where exactly are they located?
−
#Werkt de login voor de persoon die ze moet verwerken?
+
#Does the login work for the person working with the photo's?
−
#Welk formaat hebben de foto's?
+
#Which size do the photo's have?
−
#Zijn de foto's geoptimaliseerd voor webgebruik?
+
#Are the photo's optimized for use on the web?
−
#Welke eigendomsrechten zitten op de foto's?
+
#Which property rights do these photo's have?
−
#Is de transactie tussen opdrachtgever en leverancier helemaal afgerond?
+
#Is the transaction between customer and supplier completely finalized?
  
−
===Goede resource planning dubbelcheckt en houdt een flinke buffer in tijd===
+
===Good resource planning double checks and allows for a royal time buffer===
−
::Input: "De foto's zijn klaar gezet op de bekende plek op onze website, als je inlogt dan kun je ze downloaden"
+
::Input: "The photo's can be found on the usual place on our web site. Just log in and you can download them."
 +
::Answer:
 +
#Where exactly are they located? ''Send a URL please.''
 +
#Does the login work for the person using the photo's? ''Confirm the first successful login of the person using the photo's please.''
 +
#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.''
 +
#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>.''
 +
#Which property rights do these photo's have? ''Confirm the delivery under purchasing conditions of the customer in case <url>.''
 +
#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.''
  
−
::Antwoord:
+
==Example 2: archiving/packaging a site==
−
#Waar staan ze precies? ''Stuur ajb de URL mee.''
+
If you have to develop a template
−
#Werkt de login voor de persoon die ze moet verwerken? ''Bevestig even de eerste geslaagde login door de verwerker van de foto's.''
 
−
#Welk formaat hebben de foto's? ''We hebben 200x300 pixels afgesproken, filenaam voldoet aan deze structuur en de randen zijn afgerond. Bevestig even in deze case <url> dat ze daaraan voldoen.''
 
−
#Zijn de foto's geoptimaliseerd voor webgebruik? ''Kun je akkoorden van marketing afdeling en de technische beoordeling uploaden in de case <url>.''
 
−
#Welke eigendomsrechten zitten op de foto's? ''Bevestig nog even dat de levering onder in de inkoopvoorwaarden van de afnemer in case <url>.''
 
−
#Is de transactie tussen opdrachtgever en leverancier helemaal afgerond? ''Kun je bij de oplevering meezenden de stand van evt. openstaande verplichtingen van de afnemer van de foto's.''
 
  
 +
===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!"
  
−
==Voorbeeld 2: site inpakken==
+
::Answer:
−
  Als je een template moet ontwikkelen
+
#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>.''
 +
#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.
 +
#In case of Dropbox: include share details for the user ''Confirm the first successful login of the user of the zip-file.''
 +
#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.
 +
#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.
 +
#Which access privileges does the site have? Could you paste those roles and logins in the case <url>.
  
−
===Goede resource planning dubbelcheckt en houdt een flinke buffer in tijd===
+
===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: "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."
  
−
::Antwoord:
+
The recipient doesn't bear in mind that:
−
#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>.''
+
#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".
−
#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.
+
#He decreases the buffer for the user.
−
#Indien Dropbox: stuur shares voor de verwerker mee ''Bevestig even de eerste geslaagde login door de verwerker van de zip''
 
−
#Wanneer ben je voor de verwerker van de zip beschikbaar voor uitleg morgen ddd. <datum>? Het misschien niet nodig, maar je weet nooit.
 
−
#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.
 
−
#Welke toegangssrechten zitten op de site? Zou je die rollen en logins willen plakken in de case <urls>
 
−
 
 
−
===Slechte resource planning gaat uit van goed vertrouwen===
 
−
::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:
 
−
#Hoe klein de verschillen ook zijn: er zijn verschillen en dat betekent even veel werk als "grote verschillen"
 
−
#Hij verkleint de buffer voor de verwerker
 

Latest revision as of 15:02, 4 January 2012

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
 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?

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>
  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.
Retrieved from "http://wiki.2value.nl/index.php?title=Resource_planning/en&oldid=4739"