Comprehensive Exam Support
Lifetime PSD Certification Validity
Globally Renowned PSTs Trainer
High Success Rate
- Build and deliver working software by applying modern Agile engineering practices and supportive DevOps tools.
- Experience real collaboration between Developers, Product Owner, and Scrum
- Understand the synergy between the various elements of Scrum and complementary practices.
- Master in the quest of building and delivering a high quality and valuable product.
Origins of Agile
- Many people entering the Agile world see the Agile Manifesto as the beginning of the world, where it was really the summing up of much previous work. Anchor the ideas of Agile development in earlier work, giving the learners continuity from the past to the present.
- The 2001 Manifesto for Agile Software Development is still the anchor document for all forms of Agile development. Make clear that the Agile Manifesto is a set of values, not a prescription for a particular type of process. Also, learners should be introduced to the fact that the values on the left are preferable to those on the right.
Understanding the Agile Mindset
- Many people come to Agile looking for “the Agile process”. However, while some processes and methodologies may be more supportive or common in Agile organizations than others, the mindset must come first. Introduce Agile as a mindset and explain that agility is achieved through both “being” and “doing” Agile. The Agile mindset is characterized by things like valuing early failure for learning, collaboration, continuous improvement, continuous discovery, etc.
Establishing the Agile Mindsetn
- Experiencing the Agile mindset is the best way to establish it in a learner Allow the learner to experience situations in which the Agile mindset is likely to be different from their current way of working, so the learner can internalize the difference experientially, not just in concept
- One anchor of Agile development is incremental development. Introduce the concept and value of incremental development, and how it differs from effort-based or task-based management.
- Many people, even understanding the idea of incremental development, can’t see how to break work into small, value-centered work items and track their progress. Develop and practice techniques for breaking problems into value-based parts and tracking progress against them.
- It is easy to lose sight of the cost of rework in incremental-iterative development. Introduce and highlight why Agile developers need to keep an eye.
The Scrum Framework
- How is the Scrum theory implemented through time-boxes events, roles, rules and artefacts? How can these be used most effectively? We will experience why the Scrum framework is constructed as it is and how you as Scrum Master can effectively use Scrum to control risks and create maximum value.
Scrum Roles – Product Owner, Scrum Master and Development
- Who is supposed to be a good product owner? What Product Owner does in Scrum? Do they write stories or maximize value? Why do we need a Scrum Master? Who decides Scrum Master for the team? What’s the meaning of a Self-Organized Development Team? Is a Self-organizing team good enough or we need a self- managed team? Developers are cross-function or Development Team is cross-functional?
The Definition of Done & Acceptance Criteria
- Are you able to deliver a truly done product? What “DONE” means in Scrum and why it is important? Workshop focuses on differentiating DONE and UNDONE but also brings discussion about Technical Debts. Participants have to learn the meaning of DONE increment by defining definition in the workshop. Why not to have technical debt is critical to a growing organization? How Acceptance Criteria is different from Definition of DONE?
Working with organizational challenges
- Why change is hard and what can be done to make it real? What organizational changes needed to see the real benefits of Scrum?
Working with Product Vision
- From concepts/ideas that may be vague, product owners are taken through the steps to turn this into a tangible and valuable artefact: a product vision statement. In a group exercise, the product vision statement is developed using proven techniques such as Elevator Pitch, Lean Canvas and Product Box. From the product vision statement, a story map is developed, breaking down the vision into a manageable number of steps or functional areas, depending upon what best suits the product. With this initial outline in place, high-level functional requirements are written, introducing the concept of user stories and epics.
Writing User Stories and Story Mapping
- The story map is populated by the group writing user stories to fulfil each of the product features, ensuring the stories remain aligned with the product vision and value drivers. Will have an understanding about how to split complex features into manageable stories.
Release planning in Agile
- The planning exercise is repeated a number of times using different criteria such as risk, value, complexity, size and marketability.
- Identifying and responding to non-functional requirements to ensure they don’t get lost in the process of defining product success and lead to hidden risks.
Using Agile metrics
- Using key metrics and visualizing them with cumulative flow diagrams to help see where work is and how to improve the flow from concept to reality. Helping product owners to focus upon the right metrics and avoid those metrics that drive undesirable behaviors in development teams and by stakeholders.
Working with the development team and stakeholders
- Understand the role of the product in relation to the development team, how best to support them and what they need from a product owner to be effective in their role. Working with stakeholders, keeping them informed of progress and risks, influencing their decision making and managing expectations.
Tracking and Measuring Project Success in Agile
- How to measure the success of an agile project in the ever-evolving requirement? Discussion around key metrics like business values, velocity chart, release burndown and sprint burndown. How to incorporate feedback in the forecast and how to forecast the project completion date.
Essential Elements for Agile Way of Working
- Agile way of working has become buzzwords after the ING case study and recent adoption at ANZ. Let’s understand the pros and cons of the agile way of working. Will have a discussion around various models for organization agility and way to adopt. The focus will be on owning a roadmap for organization agility vs renting processes.
There are no prerequisites to attend the Applying Professional Scrum for Software Development™ Training in Singapore and or to take up the exam. However, it is always recommended that you go through the Scrum Guide very well.
We offer a 3-day Scrum for Software Development™ training, aimed at beginning Scrum for Software Development™ that can lead to your Scrum for Software Development™ certification. Download the brochure and check the different Focus Areas covered within these 2 days of training.
This course has the Professional Scrum Developer level I (PSD I) as an associated credential. All participants completing the Applying Professional Scrum for Software Development course receive a password from taking the PSD I assessment. This industry-recognized certification requires a minimum passing score on the associated rigorous assessment. Scrum.org maintains a public list with everyone holding a PSD I credential.
- High Success rate
- Join Our Dynamic Community
- Training from Recognized Trainer
- Post-workshop support by the Coaches
Our clients praise us for our great results, personable service, expert knowledge, and on-time delivery. Here are what just a few of them had to say:
Funding & Price Chart
|Individual Sponsored||Company Sponsored* (Banking and Finance)||Company Sponsored* (Non Banking and Finance)|
|Singaporeans age 40 and above (90% funding)||Singaporeans age below 40 and all PRs (80% funding)||Singaporeans age 40 and above (90% funding)||Singaporeans age below 40 and all PRs (80% funding)||(No Funding)|
|Full Course Fee before GST||$3,500.00||$3,500.00||$3,500.00||$3,500.00||$3,500.00|
|Total Course Fee||$3,745.00||$3,745.00||$3,745.00||$3,745.00||$3,675.00|
|Less: IBF Funding||$3,370.50||$2,996.00||$3,150.00||$2,800.00||NA|
|Net Fee Payable||$374.50||$749.00||$595.00||$945.00||$3,675.00|
The Applying Professional Scrum for Software Development course is intended for all Scrum Team members to develop and deliver software-based systems. It includes architects, analysts, programmers, database developers, testers, managers, IT-Operations, and others, including Scrum Masters and Product Owners.
The technical skills are always helpful, Applying Professional Scrum for Software Development course provides the greatest value if the whole Scrum Team (Developers, Scrum Master, and Product Owner) attend together and experience the power of real teamwork.
Participants will experience real-world challenges and issues, and through a series of Sprints will learn how to continuously improve the way they perform their work. The course teaches how Agile engineering practices and supportive DevOps tools complement Scrum and further advance a team's capabilities.
Undertaking a Professional Scrum Master™ course and earning a certification establishes several new opportunities for a professional.
Some of the most significant ones are:
- Earning the status of an industry-recognized Professional Scrum Master™.
- Get remarkable recognition throughout the industry.
- The capability to take on projects that require knowledge of SCRUM management.
- The ability to market their skills and thus negotiate better benefits at the current workplace or new ones
The main topics that are covered in the PSD training are:
- Using Scrum Framework to develop a product
- Working within a self-organized Scrum Team
- Managing requirement with Specification by Example
- Test-Driven Development & Acceptance Test Driven Development
- Agile Testing with test automation and exploratory Testing
- Pair Programming & Mob programming
- Software Craftsmanship & Emergent Design
- DevOps with Scrum and Kanban
Follow the steps to Enroll for the course.
- Enroll for the course.
- Pay the training fee, which is inclusive of the exam fee
- After the successful completion of the course, participants will receive a password to attend the PSD I assessment.
No, the Applying Professional Scrum for Software Development™ Certification doesn’t need renewal.
This course is intended for all members of a Scrum Team involved in developing and delivering software based systems including: architects, analysts, programmers, database developers, testers, managers, IT-Operations and others, including Scrum Masters and Product Owners.
Yes, you can cancel your enrollment if necessary. We will refund the course price after deducting an administration fee. To learn more, you can view our Refund Policy.
Our Applying Professional Scrum™ for Software Development training are currently held online and anyone with a stable internet from anywhere across the world can benefit from this to get Professional Scrum™ Software Development Certified.
Should you have any more questions, please email us at email@example.com and we will be happy to get back to you.