June 7th, 2010 by Mohamed Aamer

Agile is a buzz word it’s considered as one of core business values for corporate, it’s Business Agility, and in software development, it’s Agile Development. Agile is about ability to quick adaption to changes, we can call it flexibility.

Agile software development was raised up with Agile Manifesto since 2001, WOW..! It’s not new concept

Agile get into Enterprise Resource Planning (ERP) implementation recently, ERP implementation is more into waterfall model, Agile ERP implementation become valid since most of ERP implementation projects have customized solution over integrated platform

Microsoft Dynamics Sure Step 2010 have new feature in project type is Agile Implementation for Microsoft Dynamics ERP  MS Dynamics AX and MS Dynamics CRM

Waterfall and Agile

Waterfall is classic implementation model staging from Analysis, to Design,  to Deployment, and finally Operation it works for MS Dynamics Sure Step project types (Enterprise, Standard, Rapid, and Upgrade) those project types have different customization levels except Rapid  has no customization or minimal customization

Agile implementation model is associated with an iterative, incremental process for developing Microsoft Dynamics Solutions. This Project Type gives customers greater control over the final solution because they can quickly change the direction of solution development and implementation from one sprint cycle to the next. “MS Dynamics Sure Step 2010 description”

Analysis, Design, phases are called Agile preparation and Development phase called Agile Execution those phases are performed iteratively

The development phase in agile execution operates in Scrum development model,  life cycle is divided to 30 – days sprint cycle  and daily sprint cycle contains analysis, design, coding implementation and end up with solution test, and finalizing product specification (feature list)

Here is how it goes;

Solution Backlog; where the solution feature list is listed

Release Backlog; where identify and prioritize set of features to be developed during 30 day sprint, and identify each feature time estimation (story point),

Sprint Backlog; is the breakdown of release backlog according to feature priority and estimation it could be 3-days to one month (daily sprint)

User story; where descript feature business function, users (roles), and test script (less documentation)

Defect Backlog; where identify and reporting system bugs

Standup daily meeting; what we did (status), and what we have today

To know more about Scrum in 10 min check this video Click Here

When choose MS Dynamics Sure Step Agile ERP Implementation model

It’s not applicable to apply Dynamics Sure Step Agile Implementation model, here under circumstances  to be considered while decide the Project Type in the Diagnostic phase, it’s not limited to:-

  • Customer requirements are not fully defined known Up front
  • Customer can accommodate key user with development team during sprint execution
  • MS Dynamics ERP implementation needs customization (development)
  • There will be interface/integration with third party application

 Check out Microsoft Dyncmics Sure Step for an Agile world, enjoy this snack Click here

 References

  • Microsoft Dynamics Sure Step 2010
  • Wikipedia
Tags: , , ,
Posted in MS Dynamics Sure Step | Comments Off on Sure Step Agile Implementation
Comments are closed.