You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
what is the best practice to start on Jira to manage an ERP Project ?
as you know the ERP Project is divided into Modules and each Module has many functions.
Anyone here who managed an ERP software from scratch on Jira?
Appreciate your support !
Thanks in advance.
@Ali Noureddine Welcome to the Atlassian community
I have used Jira to manage many ERP implementations and ongoing support. Jira is just a tool to make it all happen. What is most important is having sounds processes that Jira is then used to support. I would suggest looking at how you plan on running your project, how you will break up your technical and functional teams and their areas of responsibility. Also take into consideration your reporting structure and how the teams will be working together. This should help you define workstreams, areas of responsibility and reporting lines. From here you will be able to look at how each team will work, what their processes will be to complete work and how they will interact with the other teams. You can then build out the processes and policies around the defined teams and work. The processes can then be built out as workflows in Jira within and across projects.
When I implemented an Oracle ERP the structure of the teams, how we would be working and reporting lines made sense for us to have a single project and organize work by issue type, components, sprints and releases.
When I implemented Workday the structure of the teams, how we would be working and reporting lines made sense for us to have 5 different projects. We still used issue types, components and labels to organize work. Some work was done in sprints but others work was done across projects and were related to tenant builds.
In both cases we used workflow to enforce processes and those were clearly defined and documented.
Really it comes down to defining what will work best for your team and how you are running the project. In all cases we made adjustments at first to improve and simplify processes. Being able to take time at the beginning to improve everything will pay dividends in the end and ensure for a smooth project delivery.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.