Our instructors have been
promoting and teaching courses in Singapore, India, Brazil,
USA and Canada.
|DAD has evolved into|
Disciplined Agile 2.0
With the evolution of DAD to DA2.0, the Consortium has evolved the certification levels to reflect the standards set within the agile community. As of today, we will move away from certifications based on "Belt" levels to certifications based on being a Certified Disciplined Agilist. See the table below to map your previous accreditation to the new accreditations. All certification and retention requirements remain the same. Please see Disciplined Agile Certification for details.
Mark will be providing an overview of the new structure in the upcoming webinar as noted below.
As a Disciplined Agilist, are you using the logo and certification initials in your signature line?
We congratulate our most recent Certified Instructors: Valentin and Saket!
On June 25, Scott Ambler presented Disciplined Agile Outsourcing. We had great response to both the registration and attendance!
Remember to retain your current belt level, webinars will be held on the third Thursday of each month, 9 times per year, not including July, August and December. Register to keep current on Disciplined Agile and to maintain your certification.
For those that attended the first webinar, your profile was updated by the administration to include your 1 hour of certification renewal.
|Upcoming Speaking Engagements|
| Meet the DAC Advisory Council |
We would like to welcome our
Disciplined Agile Consortium Advisory Council (DAC-AC).
Please read more about your new council!
By Simon Powers
At a large city council in the UK, I was asked to run an organizational transformation of about 500 people with a few development teams. Most people worked in other areas that digital delivery.
Scrum and XP practices were an obvious choice for the individual teams, however, the details of how this might work across teams and within the wider organisation were not clear.
None of the other frameworks provided guidance on how to start streams of work and so the DAD inception phase become a guiding light in defining what this would look like. Using the survey data as evidence of how others were achieving this, we set a time box of 4 weeks for inception.
To enable this to happen it was essential to review the architectural process of planning, modelling and governance. We needed a pull model to further enable and not to slow down teams and to make sure that they were included in the governance process. The DAD framework gave us both the process and the lightweight models we could use.
This significantly reduced up front planning, which in turn reduced the entire cycle time from idea to deployment. This was achieved whilst decreasing the overall technical risk of the project.
The deployment and support was also brought in-line with agile values by using the DAD framework. Traditional gateways caused lots of upfront documentation, delay, and often technical rework. These were eliminated by including the devops and support teams in the iteration or iteration meetings. This followed the DAD transition phase and again hugely reduced work, risk and cycle time.
DAD continues to offer guidance to these teams and the wider organization.
Copyright © 2015 Disciplined Agile Consortium. All rights reserved.
|You are receiving this message because you opted in at http://www.disciplinedagileconsortium.org/|