Difference between revisions of "FAQ/Contract management/en"

From 2value wiki 2
Jump to navigation Jump to search
(Created page with "==Can you please provide the details of how specific parts of the website will work?== ''As there is a lot of content work to do in this area. Particularly the related informatio...")
 
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{Languages|FAQ/Contract management}}
 +
[[Category:FAQ]]
 
==Can you please provide the details of how specific parts of the website will work?==
 
==Can you please provide the details of how specific parts of the website will work?==
''As there is a lot of content work to do in this area. Particularly the related information and featured slot on the category page despite repeated requests.''
+
''Particularly the related information and featured slot on the category page despite repeated requests. (The first request was during your visit)''
 
In my perspective: How can 2Value provide the way specific parts of the website will work upfront, while the (content structure of the site  that should the) basis for template-development is still changing (see summary https://service.2value.nl/stl/case/21572)?
 
 
 
===Begin weg===
 
K2 is a functionality block that had to be mastered by STL before we style it the first time. Hence in this order, in my view it is an interdependent effort to improve it. The reaction I get from Ruud/Angie is that the preparation of the resources is still going on until today, instead of being available upfront. That is an issue I would very much like to discuss first, because it is the source of extra work and continuous iterative development. See the various cases in SprintX that describe/analyze the situation. Having said that I am very delighted to see how we work together. But we have to be realistic: the startoff point (resources) for the templating effort was not balanced (in hindsight). And I am a bit bit confused by your comment: it should have been taken care of together allready.
 
 
 
So please get in contact with Ruud or Angie to solve this sequence - issue (what is first, what is next) and try to reach mutual understanding. Of course I expressed your wishes to pick up the most important things first after our first phone call in June. And that is what they did after I created special cases for it. But they can not bend iron with their bare hands.
 
 
 
The good thing is that because of the fact that STL got access to the first template delivary within 6 or 7 days after our meeting (!) on a testserver it became clear how the real condition of the resources were and how to improve step by step. Please continue the good work together, but it must be clear for all parties that 2Value is responsible for the service of building the template and STL for the functionality. It was and still is a STL website.  In my opinion we already have been too busy on the STL part of the job. We alerted right away.
 
  
Just wanted to elaborate on this, because the neutral reader of your comment might conclude that 2Value is not responding well. Maybe I am not getting quite right what you wanted to express, sorry if that is the case. Hope Ruud/Angie and you will be in touch soon.
+
In my perspective: How can 2Value provide the way specific parts of the website will work upfront, while the (content structure of the site  that should the) basis for template-development is still changing. Just wanted to elaborate on this, because the neutral reader of your comment might conclude that 2Value is not responding well. Maybe I am not getting quite right what you wanted to express, sorry if that is the case.
 
 
===Einde weg===
 
  
 
==It's a very small detail? Are you seriously suggesting this would hold up the project?==  
 
==It's a very small detail? Are you seriously suggesting this would hold up the project?==  
''Anyway here is the amendment in three languages. It is fine for it to go over two lines - attached images in EN / FR and it is fine.''
 
 
This case is in scope (sprint 2). The text you commented on, was a [partial copy  of Ruud/Angie's summary (https://service.2value.nl/stl/case/21572). I will asked Ruud wether he agrees that it is a small issue.
 
  
 +
I will asked the associate whether he agrees that this is a small issue. It is my role as a contract manager to make possible extra work issues explicit in cases, developers have to alert & assess the extra time needed / report time spend on unforeseen issues. Hope that clarifies.
  
 
==Could you clarify - how is this more work for anyone other than us?==
 
==Could you clarify - how is this more work for anyone other than us?==
  
I can just respond in general with a clarification: The whole issue was not in the RFP and therefore per definition extra work. If there is no or little work needed: great, it then will have no impact! But please note that every analysis, communication, alternatives, proposal for solution costs time and our time has to be paid like anyone elses time?
+
I can just respond in general with a clarification: The whole issue was not in the RFP and therefore per definition extra work. If there is no or little work needed: great, it then will have no impact! But please note that every analysis, communication, alternatives, proposal for solution costs time and our time has to be paid like anyone else's time?
 
 
It is my role as a contractmanager to make possible extra work issues explicit in cases, developers have to alert & assess the extra time needed / report time spend on unforeseen issues. Hope that clarifies.
 
 
 
==Vraag is niet duidelijk==
 
 
 
Question: To which PHPMyAdmin you do not have access? I guess Ruud's remark was concerning the Akeeba backup files.
 
 
 
Request: Ruud, do you need a new Akeeba backup or do you dare to continue with the Plugin remains in de DB or do you want Enis to get access to the PHPMyAdmin on the test server install to remove remnants. And if yes which test-install to be precise....
 
  
==Vraag onduidelijk==
+
==Why all these "extra work" comments, we are not done yet!==
  
I just got a list of "peep's" from Ruud and Angie. We will get back to you in detail about the reason for the peeps, the consequences in time & money and the links to the service cases that are involved. The main issues are:
+
I just got a list of "peep's" from the working associates. We will get back to you in detail about the reason for the peeps, the consequences in time & money and the links to the service cases that are involved. The main issues are:
  
- Styling was held back by incomplete resources
+
<list of issue>
  
- Work and advice out of scope.
+
Example
 +
- Styling was held back by incomplete resources
 +
- Work and advice out of scope.
 +
- Several interations in improvement of the site's functionality and content structure (that is interlinked with the styling effect) 
  
- Several interations in improvement of the site's functionality and content structure (that is interlinked with the styling effect)  already done with has an impact on time spend and the deadline of RFP's wishlist.
+
In some cases efforts have already been done. This has an impact on time spend and the deadline of RFP's wishlist.
 
   
 
   
We suggest to rename SprintX as Sprint3 and try to agree on another assignment for extra work done or work that still has to be done.
+
We suggest to rename SprintX as a new Sprint and try to agree on another assignment for extra work done or work that still has to be done.
 
 
Now in case https://service.2value.nl/stl/case/21572
 
  
 
==I don't see how getting it working is outside your scope?==
 
==I don't see how getting it working is outside your scope?==
  
Getting it to work is not out of our scope. It is an interdependent effort. STL does functionality, 2Value the template (we have to get it to work and "oh my": there is still work to be done which is in scope....).
+
Getting it to work is not out of our scope. It is an interdependent effort. Your tasks contain the functional aspects of website, 2Value does the template (we have to get it to work and "oh my": there is still work to be done which is in scope....).
 
 
As soon as we are advising STL, getting the resources in place and getting your part of the job done or improved: it is out of scope. No big deal as far as I am concerned: we made our estimates based on that assumption. And we report it back. It is also a way to keep our experts focussed on the deadlines and the job we promised to do first, and then afterwards help out with the other things if time & budget allows us to.
 
 
 
==Vraag onduidelijk==
 
If we still agree (see old case https://service.2value.nl/stl/case/21552)  that Slideshow functionality is a new wish (versus RFP) then read below. Otherwise: skip it and please report back what the status of this case really is.
 
 
 
 
I have to give an alert again, I am sorry, I try not to offend any one but it is my job to seperate our templating job from extra tasks like these to clean up things to make things work.
 
===Begin weg===
 
@Angie: please ask permission to actually spend the time to improve the code before we do it and deliver it. This is done by assigning Rob, ask the permission, and do not continue before Rob confirms. Please be very consistent in our way of working, otherwise we eat our budget on out of scope issues and end up delivering the in scope functionality too late ....
 
 
 
Request Angie: what time did you spend on this issue to adjust the hardcoded stuff.
 
===Einde weg===
 
 
 
==Vraag onduidelijk==
 
 
 
I did set project + type right
 
 
 
Do we agree that the menu structure (content structure) is STL work? Just checking. For now I leave this case in Sprint2.
 
 
 
==Vraag onduidelijk==
 
Set type + project right
 
 
 
What is the request? Should Rob give his preference?
 
 
 
==Vraag onduidelijk==
 
Because Angie is back to development again: Bas Vredeling does internal test with a this usertest STL scheme as a reference https://service.2value.nl/stl/case/21497.
 
 
 
Request: a list of MoSCoW findings based on our proposal. This is the internal test method (dutch): http://wiki.2value.nl/index.php?title=Testing/Bevindingen_evalueren
 
  
Planned: Time July 7th 11.30 AM
+
As soon as we are advising you, getting the resources in place and getting your part of the job done or improved: it is out of scope. No big deal as far as I am concerned: we made our estimates based on that assumption. And we report it back. It is also a way to keep our experts focussed on the deadlines and the job we promised to do first, and then afterwards help out with the other things if time & budget allows us to.
  
@Ruud/Angie: could you fix spint2 at 11:15u on the test server (that means: stop working) and send Bas the URL.
+
==How can extra work be initiated?==
 +
@Associate: please ask permission to actually spend the time to improve the code before we do it and deliver it. This is done by assigning the customer, ask the permission, and do not continue before the customer confirms. Please be very consistent in our way of working, otherwise we eat our budget on out of scope issues and end up delivering the in scope functionality too late.
  
==Vraag onduidelijk==
+
==What sequence of tasks do we perform towards the end of a sprint?==
 +
Somebody else than the developer does the internal 2Value testing. With a resource form the customers a reference: e.g. their user testing scheme.
 +
Result: a list of MoSCoW findings based on our proposal. This is the internal test method (dutch): http://wiki.2value.nl/index.php?title=Testing/Bevindingen_evalueren
 +
===Important===
 +
@Associate: could you fix the current Sprint at XX.XXu on the test server (that means: stop working) and send the URL to the tester.

Latest revision as of 16:15, 4 January 2012

Language: Nederlands  • English

Can you please provide the details of how specific parts of the website will work?

Particularly the related information and featured slot on the category page despite repeated requests. (The first request was during your visit)

In my perspective: How can 2Value provide the way specific parts of the website will work upfront, while the (content structure of the site that should the) basis for template-development is still changing. Just wanted to elaborate on this, because the neutral reader of your comment might conclude that 2Value is not responding well. Maybe I am not getting quite right what you wanted to express, sorry if that is the case.

It's a very small detail? Are you seriously suggesting this would hold up the project?

I will asked the associate whether he agrees that this is a small issue. It is my role as a contract manager to make possible extra work issues explicit in cases, developers have to alert & assess the extra time needed / report time spend on unforeseen issues. Hope that clarifies.

Could you clarify - how is this more work for anyone other than us?

I can just respond in general with a clarification: The whole issue was not in the RFP and therefore per definition extra work. If there is no or little work needed: great, it then will have no impact! But please note that every analysis, communication, alternatives, proposal for solution costs time and our time has to be paid like anyone else's time?

Why all these "extra work" comments, we are not done yet!

I just got a list of "peep's" from the working associates. We will get back to you in detail about the reason for the peeps, the consequences in time & money and the links to the service cases that are involved. The main issues are:

<list of issue>

Example
- Styling was held back by incomplete resources
- Work and advice out of scope.
- Several interations in improvement of the site's functionality and content structure (that is interlinked with the styling effect)  

In some cases efforts have already been done. This has an impact on time spend and the deadline of RFP's wishlist.

We suggest to rename SprintX as a new Sprint and try to agree on another assignment for extra work done or work that still has to be done.

I don't see how getting it working is outside your scope?

Getting it to work is not out of our scope. It is an interdependent effort. Your tasks contain the functional aspects of website, 2Value does the template (we have to get it to work and "oh my": there is still work to be done which is in scope....).

As soon as we are advising you, getting the resources in place and getting your part of the job done or improved: it is out of scope. No big deal as far as I am concerned: we made our estimates based on that assumption. And we report it back. It is also a way to keep our experts focussed on the deadlines and the job we promised to do first, and then afterwards help out with the other things if time & budget allows us to.

How can extra work be initiated?

@Associate: please ask permission to actually spend the time to improve the code before we do it and deliver it. This is done by assigning the customer, ask the permission, and do not continue before the customer confirms. Please be very consistent in our way of working, otherwise we eat our budget on out of scope issues and end up delivering the in scope functionality too late.

What sequence of tasks do we perform towards the end of a sprint?

Somebody else than the developer does the internal 2Value testing. With a resource form the customers a reference: e.g. their user testing scheme. Result: a list of MoSCoW findings based on our proposal. This is the internal test method (dutch): http://wiki.2value.nl/index.php?title=Testing/Bevindingen_evalueren

Important

@Associate: could you fix the current Sprint at XX.XXu on the test server (that means: stop working) and send the URL to the tester.