How to put agile methodologies into practice in ERP projects -3


ERP Agile

An ERP project consist of following components. In this and upcoming blogs we will try to answer what we can do in terms of being agile within each component. This blog covers the “Using the Program and Defining Requirements” and “Design” components.

Actions to take on “Using the Program and Defining Requirements”:

Effective feedback is at the heart of agility. If you are implementing a standard ERP program; a team that having the program experience early on, defining the requirements using this experience and participating in the process with the consultants is key to project success. At this phase;

    1. Have the people who have been trained on “Analysis” phase experience the program iteratively using predefined processes.
    2. Insist team members to repeat these processes specific number of times. Make sure that they are using the same data which are defined on the Setup and Data Entry phase and they are able to define new master data whenever necessary.
    3. Emphasize that feedback is essential for development phase. However, it is also important to use the know-how coming with the standard ERP. It is important to customize the standard ERP when it is really needed and adds value and not to customize just for the sake of old program habits.
    4. Emphasize the abilities that come with the new ERP program, and try to write requirements down with the new terminology that this program brings.
    5. Create awareness for the abilities your standard ERP has; agility is important for customizing the ERP solution and also for adopting it and making the most out of the new abilities that were previously not at hand.
    6. Highlight to the stakeholders the fact that not all details of the requirements are available even at this phase.
  • Look back and ask yourself how successful you are on the items above.

Actions to take on “Design”:

“Design” defines how processes will look like in the new program. Agility suggests a design which is robust and open to user interaction instead of a detailed and a final one. At this phase;

  1. Focus on functionality rather than form’s visual details
  2. Benefiting from the user experience, write the design document using the new program’s terminology.
  3. Design the integration points using the standard functionality.
  4. If alternative scenarios available for a specific case, go back to the previous phase and complete all necessary tasks to let the users decide which alternative is the best
  5. Determine fits and gaps and development tasks.
  6. Create the PBI list and determine development priorities.
  7. Look back and ask yourself how successful you are on the items above.

On the next post we will share our suggestions on other components of an ERP project.

Author : Yakup Toraman

Yakup Toraman

Bio : http://all4agile.com/en/bloggers/ 

Share :
Related Posts

Leave Your Comment