Full course available at: http://masterofproject.com/courses/agile-project-management-scrum-framework-certification-prep
Course Description
The Agile & Scrum Certification Training course imparts knowledge on the Agile and Scrum values, helps you build the requisite skills and gain expertise in the domain. The course provides immense clarity on vital concepts of scrum and agile to help you clear the certification exam in your first attempt. The course aims to make you an expert in the Scrum ways, enhancing your capability to deliver shippable products by the end of each Sprint. With the practical application of the agile methodologies you would be able to maximize business value, while mitigating potential risks.
Features
50+ Lectures
10+ Hours
Lifetime Access
100% Online & Self Paced
30 day money back guarantee!
Course Completion Certificate
What am I going to get from this course?
Learn the Agile Methodologies and Agile Project Management
Learn Scrum Framework
Learn practical implications of Scrum over a sample project
Get ready for Scrum Certification exams (PMI-ACP, CSM, PSM, CSPO, PSPO, CSD, PSD)
Learn Scrum Team
Learn Scrum Events
Learn Scrum Artifacs
Learn Extreme Programming (XP) Agile Methodology briefly.
Learn Lean Agile Methodology briefly.
Learn Kanban Agile Methodology briefly.
Learn the differences of Agile & Scrum Certifications provided by different organizations
Qualify for the 21 Contact Hours Agile Training requirement of PMI for the PMI-ACP certification.
Earn 15 SEUs under Category E: Independent Learning of Scrum Alliance
Earn 14 PDUs if you are a PMP already.
What is the target audience?
The Agile & Scrum certification is best suited for:
Team Leaders
Project Managers
Members of Scrum teams such as developers, Scrum Masters, and Product Owners
Managers of Scrum teams
Teams transitioning to Scrum
Professionals intending to pursue the Scrum Master certification
2. Agile
Birth of Agile:
• Particularly in 1990s, some developers reacted against traditional “heavyweight”
software development methodologies
• New approaches were being developed and tested, e.g. XP, FDD
• Generally termed “light” processes
• “Representatives” from several of these approaches got together in Utah in 2001
• Settled on term “Agile”
• Called themselves the “Agile Alliance”
• Developed a “manifesto” and a statement of “principles”
3. Agile
Birth of Agile:
• Agile isn’t a set of tools or a single methodology, but a philosophy put to paper in
2001 with an initial 17 signatories
• Agile was a significant departure from the heavyweight document-driven software
development methodologies
• These new methods attempt a useful compromise between no process and too
much process, providing just enough process to gain a reasonable payoff
Visit: http://masterofproject.com for full course
4. Agile
Birth of Agile:
Agile methods are adaptive rather than predictive
Agile methods are people-oriented rather than process-oriented
Visit: http://masterofproject.com for full course
5. Agile
Agile Manifesto:
• We are uncovering better ways of developing software by doing it and helping
others do it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working Software over comprehensive documentation
Responding to Change over following a plan
Customer Collaboration over contract negotiation
That is, while there is value in the items on the right, we value the items on the left more.
Visit: http://masterofproject.com for full course
6. Agile
Agile Manifesto:
• We are uncovering better ways of developing software by doing it and helping
others do it. Through this work we have come to value:
Visit: http://masterofproject.com for full course
7. Agile
Agile Manifesto:
• Individuals and interactions over processes and tools
Team-based approach
Promotes team-member interaction
Focus on team responsibility is critical
Visit: http://masterofproject.com for full course
8. Agile
Agile Manifesto:
• Working software over comprehensive documentation
Working & finished product is essential
Produce a product increment
Product might not have all functionality yet for the customers
Visit: http://masterofproject.com for full course
9. Agile
Agile Manifesto:
• Customer collaboration over contract negotiation
Promotes and facilitates collaboration
Finding The BEST!
Visit: http://masterofproject.com for full course
10. Agile
Agile Manifesto:
• Responding to change over following a plan
Frequent plans
Plans help the team and business to take decisions
Goal is to create value and embrace the change
Continuous planning improve the chances of success
Visit: http://masterofproject.com for full course
12. Agile
Agile Principles:
1st Principle: Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
Visit: http://masterofproject.com for full course
13. Agile
Agile Principles:
2nd Principle: Welcome changing requirements, even late in development. Agile
processes harness change for the customer's competitive advantage.
Visit: http://masterofproject.com for full course
14. Agile
Agile Principles:
3rd Principle: Deliver working software frequently, from a couple of weeks to a couple
of months, with a preference to the shorter timescale.
Visit: http://masterofproject.com for full course
15. Agile
Agile Principles:
4th Principle: Business people and developers must work together daily throughout
the project.
Visit: http://masterofproject.com for full course
16. Agile
Agile Principles:
5th Principle: Build projects around motivated individuals. Give them the
environment and support they need, and trust them to get the job done.
Visit: http://masterofproject.com for full course
17. Agile
Agile Principles:
6th Principle: The most efficient and effective method of conveying information to and
within a development team is face-to-face conversation.
Visit: http://masterofproject.com for full course
19. Agile
Agile Principles:
8th Principle: Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace indefinitely.
Visit: http://masterofproject.com for full course
20. Agile
Agile Principles:
9th Principle: Continuous attention to technical excellence and good design enhances
agility.
Visit: http://masterofproject.com for full course
21. Agile
Agile Principles:
10th Principle: Simplicity--the art of maximizing the amount of work not done--is
essential.
Visit: http://masterofproject.com for full course
22. Agile
Agile Principles:
11th Principle: The best architectures, requirements, and designs emerge from self-
organizing teams.
Visit: http://masterofproject.com for full course
23. Agile
Agile Principles:
12th Principle: At regular intervals, the team reflects on how to become more effective,
then tunes and adjusts its behavior accordingly.
Visit: http://masterofproject.com for full course
26. Agile
Need for Agile:
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Requirements
Analysis
Design
Development
Integration
Testing
Deploy
~7 months after requirements finalization
Visit: http://masterofproject.com for full course
29. Agile
Common Misconceptions About Agile:
• Agile is not
A “Silver Bullet” solution
An excuse for poor requirement definition
About failure to control the scope, it is about managed change
An excuse for poor design
An excuse for reducing quality
Doing more with less resources
Unstructured
Visit: http://masterofproject.com for full course
30. Agile
Agile Frameworks and Methodologies:
AGILE
Scrum
Extreme
Programming
(XP)
Lean
Kanban
RUP
Crystal
DSDM
FDD
Visit: http://masterofproject.com for full course
32. Agile
Agile Frameworks and Methodologies:
AGILE
Scrum
Extreme
Programming
(XP)
Lean
Kanban
RUP
Crystal
DSDM
FDD
Visit: http://masterofproject.com for full course
33. Agile
Extreme Programming (XP):
• XP includes some management elements but emphasizes technical practices more
and is therefore more of an agile engineering methodology
• In XP, the “Customer” works very closely with the development team to define and
prioritize granular units of functionality referred to as "User Stories"
• The development team estimates, plans, and delivers user stories in the form of
working, tested software on an iteration by iteration basis (typically every 1-3 weeks)
Visit: http://masterofproject.com for full course
34. Agile
Extreme Programming (XP):
• Values
Simplicity
Do only what is needed
Communication
Everyone is part of the team
Face-to-face and daily communication
Visit: http://masterofproject.com for full course
35. Agile
Extreme Programming (XP):
• Values
Feedback
Early delivery
Make any needed changes
Respect
Every team member deserves respect
Visit: http://masterofproject.com for full course
36. Agile
Extreme Programming (XP):
• Values
Courage
Tell the truth
Plan to succeed
Visit: http://masterofproject.com for full course
38. Agile
Lean:
• Lean is an iterative agile methodology which owes much of its principles and
practices to the Lean Manufacturing approach also known as ‘just-in-time
production’, and pioneered by Toyota.
Visit: http://masterofproject.com for full course
39. Agile
Lean:
• 7 Principles
1. Eliminating Waste
2. Amplifying Learning
3. Deciding as Late as Possible
4. Delivering as Fast as Possible
5. Empowering the Team
6. Building Integrity In
7. Seeing the Whole
Visit: http://masterofproject.com for full course
40. Agile
Kanban:
• Kanban is an agile methodology for managing the creation of products with an
emphasis on continual delivery while not overburdening the team.
• Underlying mechanism for managing the production line can be applied on
software development.
Software Development Pipeline
Feature
Requests
Improved
Software
Visit: http://masterofproject.com for full course
43. Agile
Kanban:
• 3 basic practices:
• Visualize what you do today (workflow): seeing all the items in context of each other
can be very informative
• Limit the amount of work in progress (WIP): this helps balancing the flow-based
approach so teams don’t start and commit to too much work at once
• Enhance flow: when something is finished, the next highest thing from the backlog is
pulled into play
Visit: http://masterofproject.com for full course
