Skip to main content

Some recommended Agile certifications


Agile has many different process . For the certifications I will limit the scope to Kanban & Scrum because these are the most popular agile practices

There are many companies providing these certifications so the cost will vary. I am listing few companies which provides these. They are leaders/pioneers in this space & I have undergone/reviewed their training.

Kanban


  • Foundation – Kanban Practitioner , System, design, Management ( scaling)
  • Trainer – Kanban trainer
  • Advanced – Coaching & advanced Kanban
  • Strategic  - enterprise services planning

Scrum

Jeff Sutherland & Ken Schwaber together created scrum process. They maintain the scrum guide which is the “Bible” for all scrum based training, coaching and the actual work done across the planet.

Scrum.org ( started by Ken Schwaber the co-founder of Scrum process)  - https://www.scrum.org/professional-scrum-certifications

  • Foundations/Roles based certifications - Scrum Master, Product Owner, Scrum Developer
  • Scaling – Nexus (Scaled scrum for multiple teams/programs)
  • Scrum with Kanban
  • Agile leadership

ScrumAlliance.org  ( started by Jeff Sutherland the co-founder of Scrum process)  - https://www.scrumalliance.org/get-certified
There are few others but these two are the most recognized and popular certifications companies.

Scaling Frameworks


Prescriptive
The frameworks provide instructions , best practices for almost all the scenarios the team/company may encounter. These are popular in big traditional organizations where the culture and organizational structures constrain what people are able to do. They can quickly get benefit of agile/scrum. In long term if no  proper org transformation or training is given then the scope of improvement and transformation will be limited. Without constant review there is also a risk of this becoming another checklist driven process.

SAFe
  • Provide a detailed process layer in top of Scrum to provide better predictability. Many traditional companies were able to quickly get benefit of agile /scrum practices using this framework. This might result in few transformation but the key focus is on program execution  using lean agile principles.  
  • Certification - https://www.scaledagile.com/certification/about-safe-certification/

Organic non-prescriptive
These frameworks abides by the Agile manifesto and provide the general structure and guideline to make organizational/program transformations. They are organic  in nature and demand support from everyone involved. These frameworks results in a better long term transformation to create a culture which can sustain itself.

Large Scale Scrum (LeSS)
  • The acronym indicates less artifacts, less process, and fewer roles
  • Popularized by Craig Larman & Bas Vodde. Their books are still the de facto standard for scaling agile - Scaling Agile & Lean DevelopmentPractices for Scaling Lean and Agile Development
    LeSS is scaling Scrum teamwork up and out without adding layers or processes. The key focus is on customer centric learning for better product development




Lean startup

“Lean Startup” is a system for developing a business or product in the most efficient way possible to reduce the risk of failure.
It is an approach for launching businesses and products that treats all product and business ideas as assumptions (or hypotheses) that must be validated by rapid experimentation in the marketplace.  The approach relies on scientific experimentation, iterative product releases, and customers feedback to generate validated learning.
There are no certification yet but this is the most popular model used in new product development.

Spotify model

Event though there is no “coaching” or certification from another company ( or from Spotify)  many companies are using Spotify model to scale their  companies. The key success factor of Spotify model was to create a learning culture which was open to continuous  improvement without too much hindrance from management / bureaucracy.

My recommendation is to have the scrum/Kanban certification first and then if needed spend $ on scaling frameworks certifications

Based on my experience and exposure to LeSS , SAFe and Lean startup I will recommend Lean startup for all new product development + any non-prescriptive scaling framework for organization transformation.

Some additional reading material


Comments

Popular posts from this blog

SCRUM- Who should write a user story

Traditionally user stories (or requirements) were written by Business analysts. They used to prepare big documents after months of study. It was a herculean task. I used to get such UI/Functional specification documents. I have fixed a lot of bugs because I missed few text in such 1000 + pages document. This is not the only interesting part. Some of the requirements were so weird that I often wondered why I am creating the features which no one is going to use. If I had the option I would have recommended a better option. If the BA’s misunderstood some requirements & customers failed to correct those few words in the epic requirement then we will have a nice situation. In the agile world the story is different. Product Owners are primarily responsible for user stories. But can anyone else also contribute? Yes. Definitely yes In actual environment many users write user stories. The first requirement may come from end user. The PO, tech architect, scrum master, BA’s... anyone can up

What are the rules of scrum?

A relatively new person to scrum asked me this question last day. My answer to that person was yes. But really does the scrum have any rules? Scrum is a framework which helps us in developing software. It has very few rules and apart from those basic rules rest of them are guidelines like best practices. Some of the rules  The roles of Scrum • Scrum Master -  http://www.theagileschool.com/2012/03/scrummasters-checklist-roles.html • Product Owner • Feature Team The PDCA cycle ( http://www.theagileschool.com/2012/05/pdca-scrum-or-agile-why-is-it-important.html  )  frequent communication about risks (daily) • Plan – Sprint planning • Do – Actual engineering sprint – deliver a potential shippable code • Check – Sprint review • Act – Retrospective  The scrum guide @ http://www.scrum.org/Scrum-Guides will be a good guideline for teams/companies planning to start scrum. If you are following the recommendation in these then you are following scrum. Apart from these rest of

Product Backlog: Should you write everything in user story format?

I like user stories a lot. They help everyone talk the same language and results in a better product. User story alone does not constitute product requirement. User story is supposed to be a place holder for discussion which should happen between the team, Product Owner and the customer. This discussion result in a common understanding which along with the user story content is the product requirement. This format captures the essence of requirement without confusing the readers User Story is only one of the many different ways in which requirements can be represented. This is not mandatory in any Agile “process”. But many have made this mandatory. I have seen many spending countless hours trying to write the requirements in user story format when they could have easily written that in simple one-line sentence in few minutes.   I have seen team members refusing to even discuss the requirement until product owner rewrote the requirement in user story format. Once I