At Purely CRM, our team of seasoned CRM consultants, specializing in tailored Dynamics 365 CRM solutions, is continually seeking ways to improve communication with both our skilled developers and valued customers. Today, we’re redefining project language: it’s time to move from saying “phases” to embracing the term “releases.” Meet our Purely CRM team and Our Agile Methodology.
Stop Saying “Phases” and Start Saying “Releases”: Refining Dynamics 365 CRM Build and Release Terminology
Why Use “Releases”?
The term “releases” is more intuitive and engaging for customers, as it aligns with familiar experiences like eagerly awaiting a new smartphone update or software version. It suggests progress, excitement, and tangible enhancements. By adopting this terminology, we create a shared understanding of the features customers can anticipate in each delivery of their Dynamics 365 CRM solution.
Much like anticipating the latest features on a smartphone, our customers can look forward to enhancements that add value and functionality.
Breaking Down “Releases”
Each release is a milestone built around features that contribute to the overall solution. These features are structured as follows:
Features: Serve as the building blocks of the release, encompassing key user stories.
User Stories: Define the specific functionalities users will receive, broken down into manageable tasks for development.
Quality Assurance: Comprehensive testing ensures each user story meets expectations, with any bugs promptly addressed in subsequent updates.
To make releases even more transparent, we’ve adopted a widely recognized three-part semantic versioning system.
Understanding the Versioning System
Major Number: Represents the overall project number, uniquely identifying the customer’s solution.
Minor Number: Corresponds to the release of features (formerly “phases”). For example, the first production release is labeled as 1.0.0.
Hot-Fix Number: Tracks bug-fix releases. For instance, a bug fix following the first release becomes 1.0.1.
As we introduce new features, the Minor Number increases (e.g., 1.1.0 for the second release), while the Hot-Fix Number resets with each new feature release.
Benefits of Thinking in “Releases”
Adopting “releases” improves alignment with industry practices and fosters clearer communication:
For Customers: It provides a clear roadmap, detailing expected features and their delivery timelines.
For Developers: It streamlines internal planning and testing processes, ensuring smoother project execution.
Moving Forward
This shift from “phases” to “releases” reflects our commitment to delivering modern, impactful Dynamics 365 CRM solutions. It ensures that each step in the implementation journey is clearly defined, eagerly anticipated, and effectively communicated.
Let’s embrace this change and continue to deliver outstanding results, one release at a time.
Happy engineering!
Why Work with Purely CRM?
For close to a decade our Purely CRM team has been laser-like focused on delivering CRM solutions built solely on Microsoft Dynamics 365 CRM, combined with Power Apps and the Microsoft Power Platform. We’ve expanded our team immensely in the past years to help better serve our clients and partners. As an integral part of Endeavour Solutions Inc., a top Microsoft ERP, CRM, and Cloud consulting, our CRM Advisory, Design, and Development teams work with clients across Canada and the United States.
Reach out to explore our track record, rates, skills, and approach to discover how we can collaborate and drive YOUR SUCCESS. Ready to embark on a CRM journey with us?
Join our Purely CRM team at www.purelycrm.com/careers to discover how our AGILE approach can support your organization’s growth and success. www.purelycrm.com
