There’s a lot of talk about software delivery methodologies these days. To those not constantly reading the latest 400+ page textbooks on methodologies, it can be quite hard to keep up.
Agile methodologies such as Scrum can be great, but to work optimally they require a fair amount of education for all stakeholders involved, which is not always practical. Waterfall is considered by many as old hat, but lots of successful projects are still delivered this way. Hybrid methodologies can also work and can work practically and commercially. What is more important, across whatever methodology you use, are the techniques you use as part of these methodologies to define solutions and deliver real business outcomes.
There is a technique that I like to use which is ideally suited to Dynamics 365 and the Power Platform. It’s a great technique because:
It helps you gather real requirements aligned to the technology. We shouldn’t pretend to understand what someone else is imagining about a technology they have never seen before and try to make it fit.
It starts you thinking about the end-game very early in the process.
It helps you learn new technologies and capabilities as they are released.
By virtue of this techniques name, you are setting the bar quite low, so risk of embarrassing yourself is minimal (although conversely, partial failure here may be a very good thing).
It can provide valuable insight into estimates for future tasks.
It’s called the Shitty First Draft, hereby referred as an SFD.
As Microsoft Practice Lead for Codec in UK and Northern Ireland, I’m regularly thinking how Codec has grown a Microsoft Dynamics practice from a small team of 2 people to over 100 Microsoft ‘Power Platform‘ Consultants, in little over four years. In the past two years, our Belfast team has experienced rapid growth with exciting plans to grow further. Building teams at such a rate can challenge any company of any size, but Codec’s success has not come around by accident or luck.
To gain an insight into some of the factors that have helped Codec become both Microsoft Ireland partner of the year and Microsoft Dynamics partner of the year in successive years, here are some of the principles we’ve adopted in Belfast, and across the Codec group, to ensure that we stay the best at what we do. Continue reading “Building a Power Platform Dream Team”→
Over the past few days, I’ve spent some time doing a deep dive into the Unified Client Interface – it seems like most people have now settled on calling it UCI. I have been trying to work out some ‘better practices’ for user centered design, with the aim of improving user adoption for those users inclined, or perhaps directed, to use it.
Microsoft are clearly working towards a User Centered design through the very fact that the new interface exists and the principles they have implemented so far. Ultimately though, the user experience will be as good or bad as the decisions you make when, as a Dynamics customiser or partner, you configure it.
In April 2017 I attended SummitEMEA in Amsterdam and listened intently when Matt Barbour told us that a true Microsoft Dynamics XRM image – i.e. a CRM organisation instance with only accounts, contacts, activities and nothing else – existed internally within Microsoft. This interested me as partners have been calling out for this since the old CRM 4.0 on-premise days. At that time it seemed there were no immediate plans to do anything with it.
Fast forward one year, and this time closer to home in SummitEMEA in Dublin, April 2018 and Matt Barbour again moved the conversation on a country mile or three. I discovered that XRM no longer officially exists in name, but does exist in practice and has been renamed PowerApps. So, how does this work? Continue reading “PowerApps is dead. Long live XRMPowerApps.”→
I spent some time watching the some of the Microsoft Ignite sessions on YouTube, and the most interesting from a Dynamics point of view was Matt Barbour’s session looking at platform updates for Dynamics 365 Customer Edition v9.
One thing that was not disclosed at the preview sessions earlier this year was the addition of Auto Numbering for any entity – not just a few select core entities. From the screenshot Matt put up explaining how they are created in C#, it was enough to see how they were defined, so I wrote a web resource to allow users to create these without any code.
To download and see how it works find full instructions can be found on the Dynamics 365 Heroes blog. Hopefully this will not be required for too long as I would expect the native UI to be updated in a minor rather than a major update.
I listened with interest to Steve Mordue on the MS Dynamics World podcast today about his views on the recent announcements at the NAV Directions conference last week. Steve is a Microsoft Partner with an opinion worth listening to on everything Dynamics, but primarily CRM. As a Dynamics partner or interested customer, If you haven’t listened to the podcast I would recommend doing so, but first have a read of his blog post here which is a great read as well as includes as a bit of drama!
Listening to the podcast gave me some food for thought based on some conversations I have been having with some customers and other partners recently. With that in mind, I thought I’d share my own opinion here.
After the Dynamics 365 v9 preview sessions we are now getting a little bit more detail direct from the Microsoft website detailing what the changes mean in practical terms for users, configurers and developers.
I’ve been using apps with Dynamics 365 for some time now and they are a great way of simplifying the user interface in a way that doesn’t require you to cross reference low level security permissions with Site Map XML.
One problem that has come up time and time again is the fact that different organisations often have different types of contact because of the nature of their business. There are a lot of benefits you get from using the system contact entity, which means that creating a new custom entity for a new contact type does not always make sense.
For example, consider an organisation with multiple types of service and therefore multiple different types of customers. They have contacts which may encompass the following types, and contacts may often be one or more types of these.
Today I dropped into the Dynamics 365 Insider program for day one of a series of reveals we have all been waiting on for some time now. With the NDA lifted on what Dynamics CRM 9.0 will be, it was an interesting set of changes. To quote some of the technical leads, this is the biggest release Microsoft have made to Dynamics 365 so lets understand what is involved to make it a smooth transition.
Because of other commitments, I only dipped in and out of the sessions so I don’t have all the detail, but here’s a quick summary of the major features I took in and some of my musings around them. As I find out more, I will update this post accordingly.