Understanding Agile Development with Scrum

Understanding Agile Development
With Scrum
https://www.ifourtechnolab.com/custom-software-development

http://www.ifourtechnolab.com
• Module 1: Fundamentals of the AgileDevelopment Approach
• Agile Manifesto and Agile values, Tackling uncertainty, Customer
responsiveness, Early availability
• Module 2: Agile Development LifeCycle
• Scrum flow andartifacts, Product backlog, Sprint backlog, Sprints planning,
Scrum meetings, Sprintreview
• Module 3: Roles and Responsibilities
• Product Owner, Scrum Master, TheTeam
• Module 4: Agile Requirements Development
• Breaking requirements into user stories, Story estimation,Merging and
splitting stories
Topics included

• Module 5: AgilePlanning
• Release planning, Sprint types, Sprintplanning
• Module 6: AgileDesign
• Minimal design, Design for change, Usinginformation hiding to minimize code
changes, Lightweight design documentation
• Module 7: AgileConstruction
• Pair programming, Refactoring,TDD,CI
• Module 8: Agile Project Management
• Scrum and management, Status reporting, Sprint review agenda, Sprint
retrospective agenda, Recovery whenthings go wrong, Scaling agileprojects
Topics included

Module 1:
Fundamentals of the Agile
Development Approach

 Development that is characterized by gated stages.
 Waterfall - Most common and widelyused approach
Plan Driven Development

SDLC - Waterfall

 Requirements remains same through out the project
 Requirements are well understood
 Size of the projects are small to mid scale
 Highly structured systematic process
Plan Driven Development – Where toUse?

Software is dumb- Why?
What thecustomer
really needed
How the customer
explained it
How the project
leader understoodit
How the analyst
designed it
How the
programmer wroteit
What the beta
testers received
How the business
consultant
How the project
was documented
What operations
installed
When itwas
delivered

• What if
• The requirements required to change during the project life cycle?
• Requirements required to meet with business challenges time to time?
• Client wants to out perform the competitors by introducing the product first
in the market?
• Businesses and project stakeholders are constantly looking to improve
process andinnovate.
Project Requirements

• Value driven method
• Understand and meets the challenges of today’s business
• Offers much more value to the stakeholders
• Firm emphasis on customer satisfaction and quick ROI
• It is all via Iterativeapproach
Agile Development Methodology

Iterative Software Development

What is AgileDevelopment? –Definition
• Iterative and Incremental Software development method where requirements
and solutions evolve through collaboration between self organizing, cross-
functional teams.

AgileManifesto
• Individuals and interaction over processes and tools Working software over
comprehensive documentation Customer collaboration over contract negotiation
responding to change over following a plan.
• While, there is value in the items on the right side, we value the items on the
left more.

Principals of AgileDevelopment
1. Our highest priority is to satisfy the customer through early and continuous
delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes
harness change for the customer’s competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of
months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the
project.

5. Build projects around motivated individuals. Give them the environment and
6. support they need, and trust them to get the job done.
7. The most efficient and effective method of conveying information to and within a
development team is face-to-face conversation.
8. Working software is the primary measure of progress.
9. Agile processes promote sustainable development. The sponsors, developers and
users should be able to maintain a constant pace indefinitely.

10. Continuous attention to technical excellence and good design enhance agility.
Simplicity—the art of maximizing the amount of work not done—is essential.
11. The best architectures, requirements, and designs emerge from self-organizing
teams.
12. At regular intervals, the team reflects on how to become more effective, then
tunes and adjusts its behavior accordingly.

Flavors of AgileDevelopment

Module 2:
Agile Development LifeCycle
(Scrum)

Scrum Process

Scrum Artifacts
• Primary (Main) Artifacts
• Product backlog
• User Stories
• Product backlog sizing
• Sprint backlog
• Kanban Board (Signboard / Billboard)
• Burn-down chart
• Secondary Artifacts
• Acceptance Criteria.

Product Backlog
• List that represents customer’s needs and wants
• Requirements are always defined into user stories in a product backlog
• Managed by product owner
• Product owner can add or remove user stories

How To Create Product Backlog?
• Typical product backlog comprises following different types of items:
• Features
They are described in the form of user stories
• Bugs
It is almost same as the feature
• Technical Work
e.g. Upgrade all developer’s work station to windows 10
• Knowledge Acquisition
e.g. Researching about various JavaScript libraries.

Product Backlog- Excel Format

Product Backlog- Excel Format
• Product backlog in this manner is written in the form of user stories
• The form is like “As a, so that…” e.g. As an administrator should be able to inactive
any registered user so that such user can not login to the system
• The spreadsheet helps to divide each part of the requirements in to specific columns
• You can add columns as per your requirements like Status column.

User Stories
• User Story is written for the developer
• Expresses the increment of value to customer
• Vertical slice through the product.

User Stories
Vertical Slice
User Interface
Business Layer
Data Layer

What is Efficient User Stories?
• User Story should fit INVEST acronym
Independent Should be self containedThere should not be inherent
dependency on another story
Negotiable Can always be changed and rewritten until they are part
of a sprint
Valuable Must deliver value to thecustomer
Estimable Must always be able to estimate the size of a user story
Sized Appropriately Should not be so big to plan / prioritize
Testable Must provide necessary information to make testdriven
development possible

Backlog Sizing
• Estimating anything is a tricky task but comparing anything is simpler and better
• Sizing a backlog is all about making decision based upon,
• Complexity
• Amount of work (Efforts estimation)
• It is not about how long it will take to do the work.

Sprint Backlog
• Subset of Product Backlog
• Sprint backlog created during sprint planning meeting
• User stories and tasks to accomplish or remaining to complete from previous
sprint
• User stories will be divided into tasks during the sprint
• Task is a small chunk of a user story that can be done by any team member
e.g. Database changes required to do for a user story.

Sprint Backlog – Excel Format

Kanban Board
• Kanban is a Japanese word of Signboard or Billboard
• Kanban board is a task board
• Visible to entire organization
• Comprises,
• All tasks to be done by team during the sprint will be displayed on task board
• Setup meetings to gather requirements
• Review checks
• Research
• Testing
• Design
• Stages of coding.

Kanban Board Example

Burn-Down Chart
• Visual way to track how the sprint is progressing on daily basis
• Sprint backlog supplies the information for burn down chart
• Indicates remaining work
• Provides early indication if there is a problem in the sprint and the team may not
fulfill the commitment
• Burn down chart is used to analyze during sprint retrospection meeting about
how the sprint was progressed and where it can be improved in the next sprint.
• There are 2 types of burn down charts,
• Sprint Burn Down Chart
• Release Burn Down Chart.

Burn-Down Chart

Release Burn-Down Chart
• Used to track iteration progress against the release plan in a sprint burn down
chart

Alternative Release Burn-Down Chart
• What if,
• Requirements are changing frequently in eachsprint?
• New requirements added in the currentsprint?
• The burn down chart in such cases may not provide the correct result
• e.g. The team was expected to finish 40 story points in a sprint but
completed only 10 storypoints.
• Burn down chart should also provide such impediment ideas so for such cases,
use alternative release burn down chart.

Alternative Release Burn-Down Chart

Acceptance Criteria – SecondaryArtifact
• Set of steps that developer must complete before the story can be considered
done
• Created by product owner with the help of customer
• Upfront sets the expectation of the user story
• Helps to write automated tests or to implement TDD

Module 3
Scrum Roles& Responsibilities

Project People
Project People
Committed
Pigs
Lets talk about Pig & Chicken story
Involved
Chickens

Pig Roles
• Pigs are people who are committed to the project
• Pigs handle creating, testing and deploying of the project
• Typical scrum team size is 5 – 9 people
• 3 pig roles to make a scrum team
i. Scrum Master
ii. Product Owner
iii. Delivery Team.

Chicken Roles
• Are less committed
• They are the stakeholders and/or interested parties who benefit from the project,
but are not responsible for delivering it
• Chicken roles are,
i. Business Managers
ii. Customers / Vendors / Sponsors.

Scrum Master - Responsibilities
• Scrum master’s role is much more than a traditional project manager
• Scrum master liaises with different part of the team from stakeholders to testers
• Ensures the scrum process is understood and followed by the team
• Facilitates team meetings & remove any blockages

Scrum Master - Responsibilities
• Ensures no obstacles keeping the team from achieving the goals
• Isolates the teamfrom outside distractions
• Working with the product owner to keep product backlog ready for the next
sprint.

Scrum Master - Characteristics
• “Servant Leader” – Not the boss of the team but to help the team
• Helps to align the work in order to deliver value to the customer
• Point of contact for outside the group
• Needs to be a top-notch communicator
• Conflict resolving ability to bring the team back on track
• Scrum master should be influential

Product Owner
• Customer’s representative to theteam
• Determines customer’s needs
• Prepares Product Road map
• Prioritize items so that team always works on items of highest customer value
• Manages product backlog
• Responsible for the sign-off of sprint deliverable–Sprint demo
• Should be motivating the team with clear, elevating goals.

Product Owner

Product Owner - Characteristics
• Visionary
• Decision Maker
• Collaborator
• Communicator
• Analytical – Tracks progress

PO,PM & SM

Product Owner Vs. Scrum Master

Delivery Team
• Group of self-organized people responsible for delivery
• Team size – 2 to 10
• Team members – Programmers, testers, front-end designers and other disciplines
• Team works on each user story to move tasks on next stage in Kanban board
• No one is a leader, everyone decide as a group what they are going to deliver.

Chicken Roles
• The project is developed for these people
• Their views are important and must be taken in account
• Should provide the resources that helps the team to get job done
• Actively involved during sprint review only
• Do attend scrum meetings time to time.

Module 4
Scrum Activities

Sprint Planning
• Sprint planning requires before the start of the sprint
• To determine which features to include in sprint from product backlog
• Stories are sized with the team via Planning Poker tool
• Stories are turned into tasks by the team
• Time estimation elicited for each task
• Team decides if they can commit to all tasks to complete in a sprint or not.

Daily Stand Ups
• Who attends?
• The Team
• Scrum Master
• Product Owner
• When?
• Daily in the same place at the same time
• No longer than 15 minutes

Daily Stand Ups
• What is to discuss?
• To discuss the progress and issues
• Each team member answer the following 3 questions,
i. What have you done since yesterday?
ii. What are you planning to do today?
iii. Do you have any problems preventing you from accomplishing your
goal? What progress has been made on existing impediments? Can the
blockage be removed? or must it be escalated? (The Scrum Master looks
after this area.)

Sprint Review
• Held at the end of the sprint
• Team present user stories that are completed
• Informal demo of the product
• Who attends?
• The team
• Product Owner
• Scrum Master
• Manager / Customer
• The meeting is a direct value addition for the customer by showing the working software
• No need for slides and mass of presentation
• It gives a chance to customer to see ROI which is not possible in the waterfall model.

Sprint Retrospectives
• Held at the end of the sprint along with sprint review
• Scrum master gives each team mate 3 color post it notes
• 3 colors to represent,
• Things that went well during the sprint
• Things that were confusing
• Things that were bad.

Module 5: AgilePlanning
&
Module 6: AgileDesign

Planning
• Important part of the project
• Planning comprises,
• Just In Time Planning
• Detailed Planning
• User Stories
• Release Planning
• Iteration Planning (Sprint Planning)

User Stories
• Short description of a feature
• Represents single unit of business value to the customer
• It is told from user’s prospective
• Format As a <type of user>, I want <some action> so that < business benefit> Or,
In order for <some reason>, as a <user role> I want <some action>
• Typically recorded on indexed card during meeting with customer
• Should always be in a language that customer understands.

User Stories
• Must be INVEST (Independent, Negotiable, Valuable, Estimable, Sized Appropriately,
Testable)
• User story shifts focus from writing about features to discussing them.
• Details can be added to user stories in 2 general ways,
i. By Splitting a user story into multiple, smaller user stories
ii. By Adding Conditions of satisfaction.

User Stories
• Who should write user story?
• Including product owner, every one in the team because involvement of
every one makes a big difference to refine each user story and its acceptance
criteria
• When are user stories written?
• Generally through out the agile project
• Specifically story-writing workshop should be held near the start of the
project / sprint

User Stories Acceptance Criteria
• Acceptance criteria should be captured during story generation
• It can be captured on the reverse side of the user story card
• It helps to find more details and identifying dependencies
• Typically each story should have minimum 3 acceptance criteria.

Types Of User Story
• There are mainly 4 types of user stories,
• Baseline User Story
• Normal User Story
• Spike User Story
• Epic User Story

Baseline User Story
• The team should start with a small and easy to size story to begin estimation
which becomes a baseline user story.
• Each user story’s efforts estimate should be relative to this story
• Baseline story’s estimate must be accurate
• If baseline story estimate is inaccurate then the whole estimation can be
inaccurate.

Spike User Story
• Story is too difficult to estimate due to lack of technical knowledge – Create spike
(alternate story)
• Spike is created for the unfamiliar technology
• Once spike is completed then development team can estimate the actual user
story
• Spike involves gaining enough technical knowledge to estimate user story
e.g. Learning accelerometer, gyroscope readings to develop motion sensing game

Epic User Story – Story Division
• Story that needs total more than one week of work is epic story
• It is usually too big to estimate
• Divide a story in smaller VERTICAL slices
• The story should work through all layers of architecture because that provides
immediate customer value.

Estimating Stories – Planning Poker
• Planning poker is a group estimation technique
• Incorporates all team members – software developers, analysts, QA-tester,
security and infrastructure experts
• Each team member brings different technical prospective
• Customerisalsoinvolvedonlytogiveanswerraised bytheteamwhileestimating.

Planning Poker – How To Play?
• Product owner reads the story
• The team discusses the feature with the customer to get more details
• The team is free to ask the questions
• Scrum maser asks the team to privately give a number to represent the complexity of
the story.

• To prevent influence, team members should not share their numbers with others
• Once all has given number then Scrum Master asks everyone to reveal their
number
• If all team member decides the same number then it is assigned to that user
story
• If numbers does not match then the team member with lowest and highest
number are asked to explain why they think so.

• After the discussion, another round of poker is played
• The process is repeated until the team has unanimously settled on a number
• In general no more than 3 rounds will be taken
• If the team is not on conclusion even after 3 rounds then the Scrum Master
should take the middle number and move on to the next user story.

Planning Poker – Advantage
• Gives more accurate estimate because we are better in comparison
• Gives different technical prospective from different team members so all possible
loop holes can be identified
• Helps the team to be on the same page.

Release Planning
• Release is made of enough stories to offer business value
• Typically it is made of 4 iterations

Iteration Planning
• Iteration planning mainly involves 3 steps,
1. Defining Acceptance Criteria
2. Splitting User Stories in to Tasks
3. Developer “In the Zone”.

Task Board

Module 7:
AgileConstruction

Agile Construction
• Agile development should be strategically implemented across the company/development of
the project
• Agile methodology construction blocks involves,
• Environment
• On site customer
• Self Organization
• Collective Code Ownership
• Shared Understanding
• Simple Design
• Refactoring
• Continuous Integration
• Pair Programming
• Testing & QA.

Simple Design
• Simple design = free of code smells
• Code smell is any symptom in code indicating potential deeper problem &
makes the system more difficult to maintain
e.g. Code duplication, Over engineering, Large classes, Dead code, Uncommunicated
names.

Refactoring
• Process of improving and simplifying the design of existing code without changing its
behavior
• Allows automated test to be written
• Makes the application more maintainable
• Legacy applications often needs to be re-factor in order to strip away dependencies so
that automated tests can be performed.

Continuous Integration
• Basic CI Workflow

Pair Programming
• Two heads are better than one – Pair programming
• Two developers share the duty of completing one user story task
• Driver & Navigator model
• Driver – Typing the code
• Navigator – Reviewing the code, Thinking about next step.

Quality Assurance
• Quality assurance is essential when creating software
• Having great practices for gathering requirements, working closely with client and
understanding all user story without getting the right product is of no use!
• Agile promotes TDD and UAT.

Quality Assurance
• “Test-driven development (TDD) is a software development process that relies on
the repetition of a very short development cycle”
• It’s a practice that adds reliability to the development process.
• TDD is a technique where you write your test cases before you write any
implementation code.
• TDD is a technique for improving the software’s internal quality.
• TDD provides ,
• Good design
• A balanced division of functionalities
• Smooth evolution
• Maintainability
• Tests provide a specification of “what” a piece of code actually does

Quality Assurance (Cont.)
• A test is not something you “do”, it is something you “write” and run once, twice,
three times, etc.
• It is a piece of code
• Testing is therefore “automated”
• Repeatedly executed, even after small changes

TDD – Life Cycle
Requirements
Design
Testing
Implementation
Deployment &
Maintenance
Requirements
Design
Testing
Implementation
Deployment &
Maintenance

Conclusion
• Implement agile methodology across the company with Agile Construction Blocks
• No code will go in production without associated test cases
• Refactoring helps to improve maintainability
• CI helps for successful increments
• TDD helps to improve quality

Module 8:
Agile Project Management

• Project management is a combination of art and science both
• You should be well versed with the principals of the project management
• At the same time you should be practical while taking decision and understanding
circumstances
• Agile project management is more about empowerment
• Agile projects are not lead by individual like project manager.
Project Management

Project Management
• Rather projects are lead by the whole team
• Agile projects works on simple processes that anyone can follow
• Who manage the agile projects?
• Project are mainly managed by both Product Owner and Scrum Master together
• Product owner is responsible for managing business aspects
• Scrum Master is responsible for implementing agile development processes.

Project Phases
• There are 5 distinct phasesfor any project,

Agile Project Phases
Initiation >> Product Backlog
Planning >> Sprint Planning
Executing >> Sprint
Monitoring &
Controlling
>> Manage Sprint
Closing >> Close Iteration &Release
Planning

Planning (Sprint Planning)
Inputs Tools & Techniques Outputs
1 Product Backlog
(Prioritized)
2 Velocity Achieved
Previously
2 User Stories (Draft)
2 Team Members’
Availability
1 Sprint Planning
Meeting
2 Estimating in Points
(Fibonacci)
2 Planning Poker
1 Sprint Goals
1 Sprint Backlog
1 User Stories Selected
1 Task Breakdown and
Estimates
1 Team’s Commitment
1 Cards on Whiteboard

Execute Iteration (Sprint)
Inputs Tools &Techniques Outputs
1 Selected User
Stories (represented by
Cards on Whiteboard)
2 TaskBreakdown
1 Collaboration
1 Test Driven Development
1 Automated Testing
1 Continuous Integration or
Daily Build
1 Test Early &Often
1 Pair Programming
1 Refactoring
1 Working Software
for Selected User Stories
2 Test Confirmations
2 Automated Tests
2 AnyRelated
Documentation

Monitor & Control Iteration (Manage Sprint)
1 Work Completed
Yesterday
2 Work Planned Today
2 Impediments Affecting
Progress
2 Working Software for User
Stories Completed SoFar
1 DailyScrum/Standup
1 DailyBurn down or Burnup
Chart
1 Review Product Frequently
/ Active User Involvement
1 Address Impediments
1 Definition of Done
1 Final Burn down or
Burnup Chart
2 Velocity Achieved

Close Iteration (Manage Sprint)
1 Work Completed
Yesterday
2 Work Planned Today
2 Impediments Affecting
Progress
2 Working Software for User
Stories Completed SoFar
1 DailyScrum/Standup
1 DailyBurn down or Burnup
Chart
1 Review Product Frequently
/ Active User Involvement
1 Address Impediments
1 Definition of Done
1 Final Burn down or
Burnup Chart
2 Velocity Achieved

Velocity
• Velocity means to find how much work you can commit in a sprint
• It better helps to estimating the features and providing commitments
• How to measure velocity –
i. Select a sprint as unit to measure velocity
ii. Add the estimation of all the tasks of the sprint
iii. At the end of the sprint add the hours of the tasks that are completed fully
iv. Tasks that are not completed will be considered as zero
v. At the end of the sprint the hours you got is your velocity.

Scrum Of Scrum
• Scrum of Scrum is analogues to DailyStand upmeetings (DailyScrum Meetings)
• Large Scale projects when there are multiple sprint teams available, each team
identifies one person to attend Scrum ofScrum
• Decision of who to send is belongs to the team
• Usually theperson chosen should be technical – programmer, designer, tester
• Generally product owner or scrum master does not selected

Scrum Of Scrum Meeting Agenda
• Scrum of scrum meeting agenda is similar to daily scrum with one more additional
question.
• The questions to be asked are,
i. What has your team done since we last met?
ii. What will your team do before we meet again?
iii. Is anything slowing your team down or getting in their way?
iv. Are you about to put something in another team’s way?

Scrum Of Scrum Example (Large Scale Project)
• Total Resources: 243 People
• Team size: 9 People in each team
• Total Sprint Teams: 27 Sprint Teams
• Scrum of Scrum meetings are held for monitoring and helping cluster of teams

Scrum Of Scrum Example (Large Scale Project)

How agile are you or your team?
• Questionnaire to ask the team members
• 42 questions present in it
• Give answer as 1 if you are 100% doing it else 0
• Take the average of the score of each team member.

42 Points Test
1. The team is empowered to make decisions.
2. The team is self-organizing and does not rely on management to set and meet its
goals.
3. The team commits and takes responsibility for delivery and is prepared to help
with any task that helps the team to achieve its goal.
4. The team knows who the product owner is.
5. Each sprint/iteration has a clear goal.
6. All team members, including testers, are included in requirements workshops.

42 Points Test
7. Requirements documentation is barely sufficient and the team collaborates to
clarify details as features are ready for development.
8. Test cases are written up-front with the requirements/user story.
9. There is a product backlog/feature list prioritized by business value.
10. The product backlog has estimates created by the team.
11. The team knows what their velocity is.
12. Velocity is used to gauge how many user stories should be included in each
sprint/iteration.

42 Points Test
13. Sprints/iterations are time boxed to four weeks or less.
14. Sprint budget is calculated to determine how many product backlog
items/features can be included in the sprint/iteration.
15. The sprint/iteration ends on the agreed end date.
16. All tasks on the sprint backlog are broken down to a size that is less than one day.
17. Requirements are expressed as user stories and written on a card.
18. The team estimates using points which indicate the relative size of each feature
on the product backlog/feature list.

42 Points Test
19. The team generates burn down charts to track progress daily.
20. Software is tested and working at the end of each sprint/iteration.
21. The team is not disrupted during the sprint/iteration.
22. Changes are integrated throughout the sprint/iteration.
23. Automated unit testing is implemented where appropriate.
24. There is an automated build and regression test.
25. Stretch tasks are identified for inclusion in the sprint/iteration if it goes better
than expected
26. The Product Owner is actively involved throughout each sprint.
27. All code changes are reversible and it is possible to make a release at any time.

42 Points Test
28. Testing is integrated throughout the life cycle and starts on delivery of the first
feature.
29. Impediments that hold up progress are raised, recorded on the whiteboard and
resolved in a timely fashion.
30. When someone says ‘done’, they mean DONE! (i.e.shippable).
31. The team uses the whiteboard to provide clear visibility of progress and issues
on a daily basis.
32. The sprint/iteration goal(s) is clearly visible on the board.
33. All user stories and tasks are displayed on the whiteboard for the duration of the
sprint/iteration.

42 Points Test
34. Daily scrums happen at the same time every day – even if the scrum master isn’t
present.
35. The daily scrum is restricted to answering the standard 3 scrum questions and
lasts no more than 15 minutes.
36. There is a product demonstration/sprint review meeting at the end of each
sprint/iteration.
37. All team members, including testers and Product Owner, are included in the
sprint/iteration review.
38. The sprint/iteration review is attended by executive stakeholders.
39. There is a sprint retrospective at the end of each sprint/iteration.

42 Points Test
40. Key metrics are reviewed and captured during each sprint retrospective.
41. All team members, including testers, are included in the sprint retrospective
meeting.
42. Actions from the sprint retrospective have a positive impact on the next
sprint/iteration.

Disadvantage Of Agile
1. Active user involvement and close collaboration
2. Requirements emerge and evolve
3. Agile requirements are barely sufficient
4. Testing is integrated throughout the life cycle
5. Frequent delivery
6. Sustainable pace
7. System structure tends to degrade as new increments are added
8. Regular changes usually corrupts the structure unless time & money spent on
refactoring
9. Has the potential to degenerate into a build & fix model.

Module 9:
Material & Certification

Top 10 Books For Agile Transformation
1
Pro Agile .NET Development With Scrum- Apress

2
Scrum Mastery : From Good to Great Servent-Leadership

3
Agile Estimating & Planning Your Sprint with Scrum

4
Continuous Delivery: Reliable Software Releases through
Build, Test,& Deployment Automation

5
Agile Retrospectives: Making Good Teams Great

6
The Agile Enterprise: Building & Running Agile Organizations

7
Agile UX Storytelling: Crafting Stories for Better Software Development

8
User Stories Applied: For AgileSoftwareDevelopment

9
More AgileTesting: Learning Journeys for the Whole Team
(Addison- Wesley Signature Series (Cohn))

10
AgileEstimating and Planning

Certification Bodies
• Popular Main 3 bodies
• Scrum
• https://www.scrum.org
• Scrum Alliance
• https://www.scrumalliance.org
• Project Management Institute
• https://www.pmi.org

Certification Bodies
• Other Bodies
• Scrum Institute
• www.scrum-institute.org
• APMG International
• www.apmg-international.com
• International Consortium for Agile (ICAgile)
• www.icagile.com
• Scrum Study
• www.scrumstudy.com
• Agile Certifications
• www.Agilecertifications.org

Certification Types
• PMI ACP (Agile Certified Practitioner) https://www.pmi.org/certifications/types/agile-acp
120 Multiple Choice Questions
• Cost: US$ 495
• CSM – Certified Scrum Master https://www.scrumalliance.org/get-
certified/practitioners/csm- certification
• Need to take 2 days Scrum Alliance Training Passing Marks: 80% Minimum
• Cost: US$ 1000 to US$ 2500
• PSM 1 – Professional Scrum Master, Level 1 https://www.scrum.org/professional-scrum-
certifications
• Starts from US$ 150

Thank you!

Understanding Agile Development with Scrum

More Related Content

What's hot

Similar to Understanding Agile Development with Scrum

More from iFour Technolab Pvt. Ltd.

Recently uploaded

Understanding Agile Development with Scrum

Editor's Notes