0

In our company, we have projects following from Customer Requirement with meeting up to Product delivery with training and documents as the full life cycle.

But for some projects, we are doing 'Task-Based works'. That is, the customer asks us to do only part of the life-cycle ... the remaining work is taken care of by them. For example, Product development has done by them but they send the result to us for Testing. As another example, we will do only Functional design specification and initial configuration. Like this, we are having some projects mostly billing as per the time sheets rather than a lump-sum price.

So, under which method do such kind of projects fall? Some referred to this as the Agile methodology. Is that correct? If not, then what is the correct terminology for such works? Currently, we are referring to them as 'Task-Based Projects'.

-1

It sounds like a good name to me.

I suppose really both types of project follow the full lifecycle. The 'Task Based' ones have 'agree tests to be run' or whatever as their 'gather requirements' step and 'hand over test report' as their 'product delivery' step.

You need a name which differentiates effectively the products your company is selling. Its more of a marketing question really

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.