Your process is one of the things you change. You hack it. You can try a change for one iteration and evaluate at the end of the iteration.
If you have a Defined Process(TM) - of whatever flavor - you're missing a big part of agile, perhaps even the most important part.
Let your process adapt to your people, your environment, your situation, your project, and your goals. Eliminate everything that isn't useful; shorten to the minimum everything that is useful.
Even if you started with Agile(TM) as defined by a Scrum Master(TM), but you're willing to change the process as you find out what doesn't work or is wasteful, you can still converge on something pretty good. You just have to keep tweaking the process, paying attention to what works and what doesn't.
Or to put it in XP terms: Pay attention to pain, not just in your technical areas but also in your processes and procedures.
This. So much this.
Your process is one of the things you change. You hack it. You can try a change for one iteration and evaluate at the end of the iteration.
If you have a Defined Process(TM) - of whatever flavor - you're missing a big part of agile, perhaps even the most important part.
Let your process adapt to your people, your environment, your situation, your project, and your goals. Eliminate everything that isn't useful; shorten to the minimum everything that is useful.
Even if you started with Agile(TM) as defined by a Scrum Master(TM), but you're willing to change the process as you find out what doesn't work or is wasteful, you can still converge on something pretty good. You just have to keep tweaking the process, paying attention to what works and what doesn't.
Or to put it in XP terms: Pay attention to pain, not just in your technical areas but also in your processes and procedures.