I have to deliver a software as pilot within 7 days. I would like to know what minimum processes can be followed so that we deliver a quality software. Should I be looking at XP, agile or Scrum methodology? I don't have too much info on these methodology. It would be great if I can get web reference on these methodology.
If you have only 7 days do don't have time to implement any other methodology than existing one or do it Ad Hoc.
Or do you mean your business is to deliver pilots in 7 days and you need a process for this? Or is it some exam question?
?:the art of a constructive conflict perceived as a destructive diagnose.
We want to deliver this to a customer and based on pilot result, he will decide if we have the capability to deliver quality software. We cannot implement exisiting one as it has lot of artifacts and just impossible to implement for a 7 day pilot. We want to show the customer that we can deliver quality software and show to him that we did followed some process. We would like to show him some artifacts as part of process implementation.
I had a look at SCRUM and though the methodology is defined for a 30 days cycle,I think we can adopt it for this pilot. The work will be incremental. So I think this methodology suits the best. Any advice/suggestion?
Right now, who would know which of your duplicate posts to answer??
"7 days" to implement any QA process - regardless of how light it is would be near impossible. If your organization is thinking about it this late in the game, then it kinda shows they have no strong interest to implement one anyway! A QA process is ideally implemented under proactive conditions with a proactive culture.
It appears that you want to backfit fiction into a broken or non-existent process, thus making it appear to the customer that the software was developed under a process. In the U.S., we have a term for that - "White Collar crime". IMHO, this is no different than faking a resume'. Take your lumps as an organization and learn from it. Honesty will work best here. If any forward-looking thinkers exist in your organization, they should be able to understand that concept.
How was the software developed? Were random bits of code thrown together until something happened or was *some* process used to determine what should happen when?
I think there is some confusion as to what is needed. Are you looking to deliver software in 7 days? If so, has it been coded? If not, without knowing the scope and nature of the project, how can we tell you or make suggestions.
If, as JB read the question, the software exists and now you must develop a nice story about the process used to create it, would you really expect us to become accessories to your goal?
Based on this statement: "We want to deliver this to a customer and based on pilot result, he will decide if we have the capability to deliver quality software. We cannot implement exisiting one as it has lot of artifacts and just impossible to implement for a 7 day pilot. We want to show the customer that we can deliver quality software and show to him that we did followed some process." I think I know the answer. However, a more precise explanation may serve you, and us, better.