© 2006 Cisco Systems, Inc. All rights reserved.Presentation_ID 1 Curriculum Release and Bug Reporting Processes November 2007

© 2006 Cisco Systems, Inc. All rights reserved.Presentation_ID 1

Curriculum Release and Bug Reporting Processes

November 2007


Curriculum Release Process Objectives

Provide a framework that is:

• Structured agreed classifications and numbering scheme

• Predictable fewer surprises about “what’s next”

• Transparent provide visibility into release decisions

• Proven based on industry best practices

• Appropriate

for both curriculum lifecycle and portfolio planning


Reasons for a Release

Entirely new course

Major framework change; e.g. CCNA 3.0 > CCNA Discovery 4.0 & CCNA Exploration 4.0

Refresh of course content without significant changes to framework

Collection of error fixes

Immediate error fix

Adaptations of existing release; e.g. translations, accessible versions, etc.


Release Types and Versioning

Initial release – version 1.0

Major release – version X.0Major framework or platform changes

May occur every 3 to 5 years

Minor release - version X.yMinor content or framework changes

May occur every 1 to 2 years

Maintenance release - version X.y (z)Minor content improvements and error fixes

May occur frequently after a major release, then tapers off

Emergency release – version X.y (z)Only if a P1 bug requires immediate response

Adaptations – same version as adapted release


Example Product Roadmap

Advanced Course

Advanced Course

Intro Course 3.0

Q1 Q2 Q3 Q4 Q1 Q2 Q3

IntroIntro CourseCourse

Major Minor Maint.

SpecialtyCourse

SpecialtyCourse

Specialty Course

3.2

Etc…Etc…

Specialty Course

4.0

Intro Course 3.0 (1)

Intro Course 3.0 (2)

Intro Course 3.1

Adv. Course 5.0

Adv. Course 5.0 (1)


Example Product Roadmap – 1 Curriculum

SpanishSpanish

Q1 Q2 Q3 Q4 Q1 Q2 Q3

English English versionversion

Initial Release

1.0

Major Minor Maint.

1st Maint

Relelase

1.0 (1)

2nd Maint

Release

1.0 (2)

Minor Release

1.1

Initial Release

Spanish 1.0

Minor

Release

Spanish 1.1

AccessibleAccessible

Etc…Etc…

Initial

Release

Accessible 1.0

Initial Release

1.0

1st Maint

Release

Spanish 1.0 (1)

1st Maint

Release

Accessible 1.0 (1)


Major Release Example

Changes in the certification, the age of the existing curriculum (>3 years), and a desire to take advantage of new delivery technology drive significant changes to the course

Major changes to chapters

→ deletion of old chapters

→ inclusion of new chapters

→ changing order of material

Change in the GUI

Major X.0 release


Minor Release Example

Certification requirements have changed, so numerous chapters need revision in order to stay current. An additional chapter needs to be added as well, but the overall flow of the course, the GUI, and the delivery mechanism remains unchanged.

Minor X.y release


Maintenance Release Example

Numerous minor changes have been made to the curriculum and assessments in response to requests from internal and external sources

Numerous bugs fixed

Maintenance X.y (z) release


Emergency Release Example

Despite careful QA procedures and testing, a Priority 1 bug is found after release and the error could potentially affect the delivery of the course.

Emergency release X.y (z)


Adaptation Release Example

Translation into Spanish has been completed on the 4.2(1) release of a course

Released as 4.2 Spanish


Errata / Bug reporting process

Maintenance releases are determined by the number and severity of reported bugs

We encourage all instructors to report bugs in the curriculum and assessments as they are discovered

View existing errata and report new bugs using Academy Connection

The Global Support Team responds to all new bug reports within 24 hours


Bug Reporting Process – Step 1

Log into Academy Connection and access the Curriculum and Assessment Quality Support page

Click Help and select Curriculum and Assessment Quality Support

OR

Click Contacts and Feedback on the Instructor Home page, click Academy Community Support, then select Curriculum and Assessment Quality Support


Bug Reporting Process – Step 1 (cont’d)

OR

Select Report Curriculum and Assessment Quality Issues on the Instructor Class Home page



Check the errata to see if the bug has already been reported using the Answers tab

Select the errata or error list for the appropriate course and category (curriculum or assessment) from the list displayed


Bug Reporting Process– Step 2 (cont’d)

Download the errata spreadsheet listed in File Attachments

Open and review the errata spreadsheet to determine if the problem you’ve found has already been reported



If your bug has not been reported, please report it!Select Contact Curriculum Team or Contact Assessment Team tab, as appropriate

Fill out form and submit – you’ll get a response within 24 hours


Conclusion

All curriculum releases will follow a standard and easily understood numbering convention

Maintenance releases will be based on the quantity and severity of reported bugs

Instructors can access errata and report bugs using the Curriculum and Assessment Quality Support Tool on Academy Connection


Documents

© 2006 Cisco Systems, Inc. All rights reserved.Presentation_ID 1 Curriculum Release and Bug Reporting Processes November 2007