This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
In Quality and Process, which need to be given Priority? Experience always accelerates the Process & Quality? But to gain experience in a particular work needs time. How this needs to be balanced in lean/Agile Process?
I don't quite see why one should have to choose between quality or process. I think of process as the way you currently do things (not the way you wish you were doing things - the way you actually do things). Hopefully your current way of doing things produces high quality; if it doesn't, it needs to be improved. As you gain experience, you should constantly improve the way you do things; the way you know that you have been successful is that you have increased quality.
Quality is experienced by the customer; process is what you do to deliver that experience. In lean, customers are the center of the decision-making process. If doing something differently delivers more customer value, then that is the thing to do.
Author of Lean Software Development, Implementing Lean Software Development, and Leading Lean Software Development