Skip to main content

AX and Scrum: Product development (ISV)

Being recently certified as a scrum master through scrum alliance I thought I would share some experiences through this blog.

Last week I wrote about what I was working on for the last 2 years (Daxeam – Enterprise asset management solution for Dynamics AX). Continuing with the spirit of sharing. I will try to post how we are building our product and provide some examples.

Our development methodology of choice is Scrum.

What is scrum?

“An agile framework that allows us to focus on delivering the highest business value in the shortest time.”

Mike Cohn – “Introduction to Scrum Methodology”

It is an incremental and iterative approach to development.

Why scrum?

The biggest advantage of scrum for me is that it allows the team to deliver the highest business value first. Then on top of that each sprint release is a potentially shippable product. Yes – in AX any mod is shippable but what scrum does is it formalize this for. Rather than being reactive, it allows you to focus on what you (team) have committed to.

How scrum works?

Below is a high level diagram showing how Srcum works.


  • One product owner priorities the product backlog (think of these as functional requirements, development requirements etc)
  • The sprint team (developers/functional consultants/testers etc) decides each sprint (2 weeks to weeks) how much work they can do by picking items from the top of the product back log (highest priority)
  • Sprint starts
  • Cycle through the sprint making sure all the stories are done. The team has committed to this so they better be sure they can finish it it.
  • Sprint ends at the fix allocated time. When you can ship the product (in AX terms you can release a fully working/tested model).

The scrum masters job is to facilitate the team and make sure everyone is following the scrum framework. Removing any impediments. Making sure the team communicates.

Enough of the intro for today. Next time I will get into the some real examples.

  • How we manage our development environments
  • Product back log
  • Task board – Visual board to see the progress of each task
  • Sprint burn down – how to see remaining work in a single graph
  • Example story and the tasks

Extra reading:

Great video in under 10minutes you get to understand what scrum is.

Must read scrum guide.

Popular posts from this blog

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi