Project Management: Process Classification

by | Feb 2, 2015 | Dynamics AX, Lifecycle Services, Project Management

“There is more than one way to skin a cat.”  That phrase has an interesting history, but it’s still amazing to me how often that saying get used today.  I was  going to use it again but instead I’ll just say there are lots of ways you can go about classifying requirements when implementing an ERP system.  I actually don’t care that much what system someone uses, as long as they have a system.  If you use the Sure Step Excel sheet to track requirements, you’ll be doing it according to the module under which the functionality exists.  We started doing that too, but we found a big problem with it – traceability.

Why Is Traceability Important?

Traceability is a big word that doesn’t get thrown around too much – however, it’s important in the context of an ERP implementation.  You need to be able to understand from where your requirement comes.  If I’m the second consultant looking at a requirement that says “Add external comments to the project invoice report”, I would say, “great, we can do that”.  However, I have no idea why that requirement exists or who originated it.  When I have the developer modify the report to add this field, who do I have test it to make sure it looks the way they want.  This is where listing a ton of requirements in a spreadsheet falls down.  It’s a lot of information that’s disconnected from anything other than a module.

You can still classify requirements against modules if you’d like, but you need to include information about who requested and why.  This is what we started doing on our first couple of projects, and it worked okay because they were smaller projections so we knew where to go digging if we had a problem.  The concept starts to get pretty difficult when you have a big project with multiple SME groups and different consultants.  We found it much easier to associate requirements with a process that the customer follows.

Process Driven Approach

At Stoneridge Software, we use a process-driven approach to gathering and tracking requirements.  What this means is that we first learn the customer’s processes, then we start to figure out what they need the system to do to support these processes.  These should be their “to-be” processes, and not just how they do things today.  We dive deeper and deeper into the processes throughout the analysis and design phase so we can get down to the task level and understand everything that needs to be done to achieve this process.  To help us define this, we’ve adopted the hierarchy that’s articulated in Lifecycle Services, which originally comes from the APQC.

By utilizing this approach, we can trace a requirement back to a process which has a defined process owner and a visual workflow so we can see where the system need fits into the process flow.  This really helps us trace back the need for the requirement and makes it easier for us to understand the importance of it in their flow.

Process Hierarchy

Here’s my representation of the process hierarchy which includes a Process Category, Process Group, Process, Activity and Task:

Process Hierarchy

In Lifecycle Services, Microsoft has used the APQC hierarchy to provide 12 process categories and their associated process groups, processes and activities.  While we agree with the hierarchy and the approach, we have found that re-classifying the process categories to fit an ERP implementation activities more closely as a better plan for us.

How We Approach a Project

When we start a project, we come in with a set of process categories and groups based on projects we’ve completed in the past.  We first try to see if the customer wants to implement any or all of these process groups and then understand what different process sets they have which we’ll need to explore.  We then put them into the broader hierarchy within our SharePoint site and Enterprise Architect so we can trace back any requirements to the processes which ultimately lead back to these process groups that were originally defined.  By using a relational model for our process tracking, we have an approach that will allow us to connect the whole project together and make sure that our plan is comprehensive and cognizant of the other parts of the implementation.

Let me know if you’re interested in learning more about this approach and I’ll continue to add more nuggets to it over the next few weeks.

Eric Newell

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Upcoming Events

april

08apr10:00 am10:30 amLicensing Preparedness for Dynamics 365 Customer Engagement

08apr12:00 pm1:00 pmMaking Project Information Management (PIM) a Priority

08apr2:00 pm2:30 pmFeatures in the Spring Release of Dynamics 365 Customer Engagement Users Can Take Advantage of Immediately

09apr11:00 am12:00 pmConfab With Stoneridge - Livestream - Portals

13apr11:30 am12:30 pmStoneridge Connect Online Keynote: Business Transformations Throughout History

14apr8:00 am5:00 pmStoneridge Connect Online - Day 1

15apr8:00 am5:00 pmStoneridge Connect Online - Day 2

15apr1:15 pm5:00 pmWhat’s New for Developers in Dynamics 365 Finance and Supply Chain Management – Online Workshop

16apr8:00 am5:00 pmStoneridge Connect Online - Day 3

22apr11:00 am12:00 pmPower BI and Reporting with Dynamics 365 Business Central

22apr2:00 pm2:30 pmNew Features for Power Apps Users

23apr11:00 am12:00 pmConfab With Stoneridge - Livestream - Internet of Things (IoT)

29apr10:00 am11:00 amStreamlining Customer Service and Enabling Your Sales Team with a Self-Service Portal

29apr12:00 pm12:30 pmUpdates to the Dynamics 365 Customer Engagement User Experience - What Technical Resources Need to Know

may

06may12:00 pm12:30 pmPower Apps Telemetry and AI Builder - Power Platform Updates

06may2:00 pm2:30 pmImprove Customer Experience with a Mobile Workforce Management Solution

07may11:00 am12:00 pmConfab With Stoneridge - Livestream - Manufacturing

13may12:00 pm1:00 pm3 Simple Sets Your Business Can Take to Embrace the Future of B2B E-Commerce

21may11:00 am12:00 pmEnterprise Asset Management and Manufacturing

About Stoneridge
Stoneridge Software is a unique Microsoft Gold Partner, with emphasis on partner. With specialties in Microsoft Dynamics 365, Microsoft Dynamics AX, Microsoft Dynamics NAV, Microsoft Dynamics GP and Microsoft Dynamics CRM, we focus on attracting the most knowledgeable experts in the field to our team, and prioritize delivering stellar solutions with maximum impact for your business. At Stoneridge, we are deeply committed to your results. Each engagement is met with a dedicated team, ready to provide thorough, tailored, and expert service. Based in Minnesota, we intentionally “step into your shoes,” wherever you are. We focus on what you care about, and develop trusting, long-term relationships with our clients.

Subscribe To Our Blog

Sign up to get periodic updates on the latest posts.

Thank you for subscribing!

X