Bruce Passed PSD I Exam on 28th October

scrumorg-psdi_certification-112

The Professional Scrum Developer Level I certification (PSO I), accredited by scrum.org founded by Ken Schwaber, is a certification for developer. Based on my hands-on experience, I scored 92.5% and passed this exam today.

This exam is quite straightforward and has some duplicated questions. There are 80 questions to be answered in 60 minutes. I finished the exam in around 40 minutes without review.

Those who passed this exam will be entitled “Professional Scrum Developer Level I”. However, advanced levels for this certification are not available today. Some PSD aspirants criticize that Scrum is not bound to software development and the PSD exam should not be software or technology centric. I believe this is one of the major concerns for scrum.org to make this exam easy taking.

A junior developer with PSM I certification and experience of version control, TDD and CI/CD would pass this exam without much effort. It’s critical to take all the Open Assessments for PSM, PSPO and PSD before you sit for this exam.

My milestones of the year are updated as follows:

  • Milestone #1: PMI + CISSP
    • 2018/04/09 ACP
    • 2018/04/27 PBA
    • 2018/06/19 CISSP
    • 2018/07/10 RMP
  • Milestone #2: ISACA
    • 2018/07/24 CISM
    • 2018/08/13 CRISC
    • 2018/08/28 CISA
  • Milestone #3: ISC2
    • 2018/09/07 CCSP (originally scheduled on 2018/09/14)
    • 2018/09/13 CSSLP (originally scheduled on 2018/09/28)
    • 2018/09/25 CISSP-ISSEP (bonus)
  • Milestone #4: EC-Council
    • 2018/10/09 CEH (originally scheduled on 2018/10/15)
    • 2018/10/12 ECSA (originally scheduled on 2018/10/29)
  • Bonus Exams: scrum.org
    • 2018/10/21, PSM I
    • 2018/10/23, ISO 27001 LA
    • 2018/10/27, PSPO I
    • 2018/10/28, PSD

Bruce Passed PSPO I Exam on 27th October

scrumorg-pspoi_certification-250_grande

The Professional Scrum Product Owner Level I certification (PSPO I), accredited by scrum.org founded by Ken Schwaber, is the entry level certification for Product Owner. After studying for a couple of days, I scored 91.3% and passed this exam today.

As far as I am concerned, this exam is more challenging than PSM I. There are 80 questions to be answered in 60 minutes. I answered all the questions in 50 minutes and reviewed them till the exam time almost expired.

The exam user interface for PSPO I is different from the one for PSM I, but the same as the Open Assessments.

For PSPO I aspirants, kindly be noted that this is not an easy test, please fasten your seat belts.

Bruce Passed PSM I Exam on 21st October

scrumorg-psmi_certification-112

The Professional Scrum Master Level I certification (PSM I), accredited by scrum.org founded by Ken Schwaber, is the entry level certification for Scrum Master. After studying for a couple of days, I scored 92.5% and passed this exam today.

This exam is harder than what I’ve thought of. There are 80 questions to be answered in 60 minutes. I finished in 45 minutes and submit without review.

The default font size for the exam is too small for me and it can’t be changed after the exam starts. Candidates can mark questions for review, but the user interface should be improved.

Scrum is a framework for a team of people to develop, deliver and sustain complex products. However, it’s not a silver bullet. Focus on the business goal and the problem you need to solve. Effectiveness is the king; it doesn’t matter what framework or methodology you adopted.

PSM I, a bonus certification for my learning goal of the year!

My Scrum Guide Issues

  • Scrum is a framework for developing, delivering, and sustaining complex products.
  • Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
    • Define “complex adaptive problems”
    • Define “value”
  • Scrum is a process framework that has been used to manage work on complex products since the early 1990s. Scrum is not a process, technique, or definitive method.
    • Define “process”
    • Define “process framework”
  • Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment.
    • Define “product management”
    • Define “work techniques”
    • Clarify and justify “the relative efficacy of your product management and work techniques”
    • Describe “working environment”
  • Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage.
    • Define the success criteria for “Scrum’s success”
    • Define the requirements for declaring usage of Scrum
  • Specific tactics for using the Scrum framework vary and are described elsewhere.
  • Scrum has been used to develop software, hardware, embedded software, networks of interacting function, autonomous vehicles, schools, government, marketing, managing the operation of organizations and almost everything we use in our daily lives, as individuals and societies.
    • Describe or clarify “develop software, …, schools, government, …”
  • As technology, market, and environmental complexities and their interactions have rapidly increased, Scrum’s utility in dealing with complexity is proven daily.
    • Define “utility”
    • Exemplify “Scrum’s utility”
  • Scrum proved especially effective in iterative and incremental knowledge transfer. Scrum is now widely used for products, services, and the management of the parent organization.
    • Exemplify “knowledge transfer”
    • Clarify “parent organization”
  • These strengths continue operating in single, several, many, and networks of teams that develop, release, operate and sustain the work and work products of thousands of people.
    • Define “work products”
    • Clarify “work products of thousands of people”
  • They collaborate and interoperate through sophisticated development architectures and target release environments.
    • Clarify “development architectures”
    • Exemplify “target release environments”
  • Significant aspects of the process must be visible to those responsible for the outcome. Transparency requires those aspects be defined by a common standard so observers share a common understanding of what is being seen.
    • Exemplify “Significant aspects”
    • Clarify “visible”
    • Clarify “those responsible for the outcome”
    • Exemplify and compare “those responsible for the outcome” with “observers”
  • A common language referring to the process must be shared by all participants
    • Define “participants”
  • Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances.
    • Define “Scrum users”
    • Compare “Scrum users” with “participants”
  • When the values of commitment, courage, focus, openness and respect are embodied and lived by the Scrum Team, the Scrum pillars of transparency, inspection, and adaptation come to life and build trust for everyone.
    • Define “Scrum pillars”
    • Clarify the definition of the Scrum pillars between the Scrum Guide and the Professional Scrum Competency as follows:
      To support the three pillars of Scrum – empirical process, empowered/self- organized teams, and continuous improvement – the Scrum framework describes 5 events.
  • During Sprint Planning the Scrum Team also crafts a Sprint Goal. The Sprint Goal is an objective that will be met within the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the Increment.
    • Define and compare “goal” with “objective”
  • At any point in time, the total work remaining to reach a goal can be summed. The Product Owner tracks this total work remaining at least every Sprint Review. The Product Owner compares this amount with work remaining at previous Sprint Reviews to assess progress toward completing projected work by the desired time for the goal.
    • Clarify “work”
    • Clarify “goal”, a Sprint Goal or Business Goal?

Scrum Guide Notes

  • The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal.
    • Goal vs Objective
  • During Sprint Planning the Scrum Team also crafts a Sprint GoalThe Sprint Goal is an objective that will be met within the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the Increment.
    • The Product Owner propose an objective for discussion; the Scrum Team reach a consensus and turn the objective into the Sprint Goal. The Development Team commits to the Sprint Goal.
  • The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint GoalThe Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.
    • One coherent function as the Sprint Goal to work together
  • As the Development Team works, it keeps the Sprint Goal in mind. In order to satisfy the Sprint Goal, it implements functionality and technology. If the work turns out to be different than the Development Team expected, they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint.
    • The scope of Sprint Backlog
  • These strengths continue operating in single, several, many, and networks of teams that develop, release, operate and sustain the work and work products of thousands of people.
    • work product is a tangible or intangible output that is completed as part of a project.
    • deliverable is a tangible or intangible output of a project that is delivered to a customer.
    • Artifacts are either final or intermediate work products that are produced and used during a project. Artifacts are used to capture and convey project information
  • To participate in Daily Scrum vs To present in Daily Scrum

Suggested Reading for SCRUM

Agility

Bruce Passed PMI-ACP Exam on 9th Apr

pmi-acp

After attending a 40-hour instructor-led course and 60 hours of study, Bruce passed the PMI-ACP Exam today. This is the second milestone for Bruce’s learning plan of 2018.

The following is the preparation list for this exam:

  1. PMI-ACP Certification ExamPrep Course from Advanced Business Consulting Inc.
  2. Pluralsight Online Courses
  3. RMC PMI-ACP Exam Prep
  4. PMI Agile Practice Guide
  5. Agile Project Management with Scrum by Ken Schwaber
  6. Exploring Scrum: The Fundamentals Paperback by Dan Rawsthorne,‎ Doug Shimp
  7. User Stories Applied: For Agile Software Development by Cohn, Mike
  8. User Story Mapping: Discover the Whole Story, Build the Right Product by by Jeff Patton