Have you ever been asked to support or extend working software with no documentation? I have. I hate having to do that. I associate my best agile CRM projects with great documentation. And some of the worst CRM projects I've had to turn around had terrible documentation.
After a few sprints, the product backlog can look a lot like my family's refrigerator. It's stacked full. Some items are out of date. I don't even know what's in some of the containers. And I don't know who put most of the stuff in there. The storytime workshop is the CRM team's opportunity to get together in the kitchen and clear out the fridge.
If you've ever waited until the end of the sprint to demonstrate a new feature to the product owner you might have had similar feedback to me. "The address lookup is great, but isn't there a way we could autocomplete addresses from an address validation service?".
I was a Dungeon Master at the Irish and European role-playing games championships when I was a kid and was a winger for Edinburgh Northern 1st XV rugby team. Find out what it is that I have against scrum masters.
The CRM development team are the people who implement the CRM platform guided by the vision and goals set by the product owner and the under the mentorship of the scrum master. It's their role to analyse the requirements, the design, configure, customise, and test features that meet those requirements.
A sprintis a time-boxed iteration of software development during which we analyse, design, develop and test working CRM software based on the highest priority items in the product backlog. What does a sprint look like on a Dynamics CRM project?
Embracing Scrum's core values is more important than perfectly adopting any of the practices. In this article, we'll explore the pillars and values in a little more detail and share some examples of the core values in practice.
My first agile CRM experience started out as a traditional, sequential, waterfall project for Premier Medical Group that quickly went sideways, almost went backwards, but turned around to become a pivotal moment in my career.
The perfect product owner is a former UN secretary general, cooks 30-minute brownies in 20 minutes, can decide what to eat before setting the menu, and is an expert cat herder. What can you do if you don’t have the perfect product owner available for your Dynamics 365?
Your Dynamics requirements specification is probably wrong. It's probably inaccurate. Probably too short for half your audience and too long for the other half. Is there is a better way? This article will highlight the fallacy of requirements.