| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

Proposal 1: The simplest proposal

Page history last edited by Joe Little 11 years, 3 months ago

This page is to propose 'the simplest thing that could possibly work' for the new CSP process.

 

It might be too simple.

 

(As always, the SA would have to also add specific 'operational' definitions to some of these things as well.)

 

***

 

1. Pre-reqs: Must have a CSM or CSPO certification.

 

2. Must have '3000' hours of real experience in Scrum.

 

That's 1.5 years of experience.

At least 1000 hours of the experience must be obtained after receiving the CSM/CSPO.

The applicant for CSP must submit a list of experience.

The applicant must get an 'independent' person to vouch for each item of experience.

Presumably most people will need more than one 'confirmer'.

Any reasonable Scrum experience is acceptable.

No more than 2000 hours will be accept in a given 12 month period.

Examples: Team member (implementer), PO, SM, Scrum Coach, Agile coach to Scrum teams, managers directly working with Scrum teams.

 

Issues:

If you work on a Scrum Team about half-time, that would credit you with about 20 hours per week.  Not 40 hours.

General management is not enough.  Only the time working for or directly with Scrum teams.

A manager fixing impediments for Scrum teams does count as experience.

Agile coach on Kanban teams does not count.

Scrum experience outside of software is fine.

Developing a course/workshop and giving that course/workshop once both count as 'experience' hours.(Intense learning about scrum.)

But giving the same course/workshop repeatedly does not count as additional experience hours.

 

Building and giving presentations on scrum or agile does count, but for not more than 25% of the experience hours. (The presentations reflect hard work in trying to make change happen.)  Again, giving the same talk or presentation repeatedly does not count.

 

It is expected that the experience requirement will increase over the years, to 4000 hours and then to 6000 hours.  Perhaps in a jump in each of the next 2 years.

 

In part this stepped implementation is done to gain some momentum for the new CSP.

 

3. Must take a 'core' CSP course from a CST.

 

At least 15 hours.

If the course is greater than 15 hours, all PDUs could still be accepted for the CSP.

For example, a 22 hour course/workshop would be reasonable.

However, CSTs are discouraged from having a single course/workshop lasting longer than 30 hours (PDUs).  (We want the applicant to get greater diversity of learning.)

 

For now, each CST can define his/her own 'CSP' core course.

Each CST must send in at least 2 pages to SA defining the course.

These definitions of the courses will be shared publicly.

At some future date, SA may put more boundaries around the content of the core course.

 

4. Must take other CSP-related courses, for a total of 60 PDUs.

 

In total, the course/workshop hours must be 60.  60 'contact' hours, not including breaks and lunch, for example.

These courses can be about any subject that the course leader and the attendee thinks is relevant to greater success with Scrum.  Technical, managerial, SM-related, leadership, culture, tools, XP, programming, Lean, etc., etc.

These PDUs do not have to be from a CST. 

These must be from a good source/person.  For now, that means the person must be a CST or the firm must be a SA-accepted REP.

At least 60 hours in total, including the 'core' course.

Courses can include workshops.

A 'course' must be for one whole day (at least) and have at least one 'leader' who can vouch that you 'did' the course successfully.

The applicant for CSP would have to submit a list of these courses.

And include one confirmation sheet for each course, confirming successful completion in the course leader's opinion.

All courses/workshops must have been listed on the SA site.  References to the SA course numbers must be made.

To help assure that the courses are of high quality, the list of courses submitted will be made public on the applicant's public SA page.  So, between the applicant wanting to take useful courses (assuming some fee or at least time cost) and the applicant's concern about other reviewing his course list could draw some conclusions, we hope the courses will be of high quality and relevant to doing Scrum well.

 

5. Must read at least 1 Scrum book and 1 'agile' book.

 

The reading must have taken place within 12 months of submitted for the CSP.

A Scrum book indicates in its title that it is mainly about Scrum.

An agile book may be any book that the reader feels is relevant to doing Scrum better. It does not have to mention 'agile' in the title.

The Agile book can be another Scrum book.

A book must be more than 50 pages.  Smaller things (booklets) do not count.

Again, the applicant's reading list will be made permanently public.  This should provide an incentive to read good books.

The applicant must have a confirmer provide an email that the applicant read the book.

 

6. There will be no exam.

 

At least initially.

 

7. Confirmation

 

The SA will spot check the applicant's claims for validity.

Any serious discrepancies will be grounds for the denial of the CSP certification, and loss of any privilege to later re-apply for the CSP certification.

Example: A 'fraud', where the applicant shows a person confirming his experience, and in fact that person does not exist.

If some discrepancies are found, the applicant will be notified and have an opportunity to explain and perhaps correct something. Example: The applicant mis-typed the confirmer's email address or the email address is no longer valid.

 

***

 

 

Comments (0)

You don't have permission to comment on this page.