Difference between revisions of "Resource planning/en"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
{{Languages}} | {{Languages}} | ||
{{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}} | ||
| − | = | + | =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: | |
| − | # | + | #Content |
| − | # | + | #Completeness |
| − | # | + | #Format |
| − | # | + | #Size |
| − | {{Ambox|text= | + | {{Ambox|text=A promise can usually be obtained, but the actual delivery ....}} |
| − | = | + | =Who does the Resource planning= |
| − | 2Value's [[ | + | 2Value's [[project manager]]. |
| − | = | + | =How is Resource planning delivered to you?= |
| − | # | + | #Initially as '''written agreements''' via e-mail, but as soon as the project starts: |
| − | # | + | #As '''cases''' in the customer group in the [[Service tool]] |
| − | = | + | =What makes Resource planning good?= |
| − | + | If everybody that has to work on a [[PCON|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: " | + | ::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: | |
| − | # | + | #Where exactly are they located? |
| − | # | + | #Does the login work for the person using the photo's? |
| − | # | + | #Which size do the photo's have? |
| − | # | + | #Are the photo's optimized for use on the web? |
| − | # | + | #Which property rights do these photo's have? |
| − | #Is | + | #Is the transaction between customer and supplier completely finalized? |
| − | === | + | ===Good resource planning double checks and allows for a royal buffer in time=== |
| − | ::Input: " | + | ::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.'' |
| − | #Is | ||
Revision as of 06:26, 6 July 2011
| Language: | Nederlands |
|---|
|
Contents
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:
- Content
- Completeness
- Format
- 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?
- Initially as written agreements via e-mail, but as soon as the project starts:
- 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:
- Where exactly are they located?
- Does the login work for the person using the photo's?
- Which size do the photo's have?
- Are the photo's optimized for use on the web?
- Which property rights do these photo's have?
- Is the transaction between customer and supplier completely finalized?
Good resource planning double checks and allows for a royal buffer in time
- 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.
Voorbeeld 2: site inpakken
Als je een template moet ontwikkelen
Goede resource planning dubbelcheckt en houdt een flinke buffer in tijd
- Input: "Als je nog even wacht, dan hebben we echt de laatste versie voor je, met alles erin!"
- Antwoord:
- 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>.
- 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.
- 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
