1. Introduction to Agile
Blue Ocean Workshops

2. Agile vs. Waterfall
January 10, 2019

3. Misconceptions Planning is not required
Only for software development projects
Documentation is not created
Team is lacking standards
January 10, 2019

4. Agile Manifesto (2001)
“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 process and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.”
January 10, 2019

5. 12 principles of Agile Manifesto
The highest priority is to satisfy the customer through early and continuous delivery of valuable software
Welcome changing requirements, even late in development
Deliver working software frequently
Business people and developers must work together daily
Build projects around motivated individuals. Give them the environment and support they need, and trust them
The most efficient and effective method of conveying info to and within dev team is face to face conversation
January 10, 2019

6. 12 principles of Agile Manifesto
Working software is the primary measure of success
Agile processes promote sustainable development. Sponsors, developers, and users should be able to sustain a constant pace indefinitely
Continuous attention to technical excellence and good design enhances agility
Simplicity –the art of maximizing the amount of work not done –is essential
The best architectures, requirements, and designs emerge from self- organizing teams
At regular intervals, the team reflects on how to become more effective then tunes and adjusts its behavior
January 10, 2019

7. Agile’s benefits Stakeholder Engagement Transparency
Early and Predictable Delivery
Predictable Costs and Schedule
Adaptable approach for best fit
Prioritized on Business Value
Focused on Users/Usability
Improved Quality
January 10, 2019

8. Where Scrum name came from?
Scrum came from game of rugby as a reminder of:
Working together toward one goal as one team
Struggling to get things done despite obstacles
Following rules of the game, an iteration after an iteration
January 10, 2019

9. What is Scrum?
(n) a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
Scrum is:
Lightweight
simple to understand
extremely difficult to master.
January 10, 2019

10. The Scrum Team Product Owner Scrum Master Development team
Voice of Customer
Scrum Master
Servant leader for team
Development team
Deliver a potentially releasable increment of “done” product
Empowered to organize and manage their own work
January 10, 2019

11. Qualities of Agile teams
Self-directing
contains no manager
Adaptive & Knowledgeable
possess or can learn necessary skills
Resourceful
able to find a solution in every situation
Committed
committed to the team and to delivering value to the customer
Trustful
develops strong inter-relationships
Collaborative
empowers self and the each other on the team to make decisions
January 10, 2019

12. The Sprint Contains time-boxed length of work
Consists of the consistent cadence of meetings
A new Sprint starts at conclusion of previous Sprint (next day)
Sprint is also called an Iteration
January 10, 2019

13. Sprint Events Sprint Planning Backlog Refinement of User Stories
Daily Scrum
Sprint Review
Sprint Retrospectives
January 10, 2019

14. Backlog Refinement Prior to the meetings: During the meeting:
PO ensures that Backlog contains appropriate and relevant User Stories based on SMART principles
PO prioritizes User Stories
During the meeting:
Participants: PO, SM, and the Team
Length: usually 8 hours for 2 weeks sprint for the team allocated 100% to the project
PO reviews each User Story
Team ask questions and adds detail to each User Story
Scrum Master and the Team estimates User Stories (PO does not participate in estimation)
January 10, 2019

15. Sprint Planning Prior to the meeting: During the meeting:
User Stories are refined
User Stories are prioritized
During the meeting:
Participants: PO, SM, and the Team
Length: usually up to 4 hours for a 2 week sprint for the team allocated 100% to the project
Each team member accepts one or more User Stories (up to each capacity)
Scrum Master adds the User Stories to the Sprint in Jira
SM start the Sprint
January 10, 2019

16. Daily Scrum Prior to the meeting: During the meeting:
The Team was assigned User Stories
The Sprint has started
During the meeting:
Participants: SM and the Team
Length: time-boxed to 15 minutes
SM displays Sprint Board in Jira
While SM displays Scrum Board, each team member speaks about each User Story in following format:
What was done
What is being done
What will be done
Impediments or issues
The SM and the Team share ideas to resolve impediments and issues
January 10, 2019

17. Scrum Board
January 10, 2019

18. Sample of Scrum Board with sticky notes
January 10, 2019

19. Sprint Review Prior to the meeting: During the meeting:
The Team has worked on User Stories and moved them to appropriate categories (To Do, Doing, or Done)
During the meeting:
Participants: PO, SM, and the Team (Demo also w/other stakeholders)
Length: up to 4 hours, longer if Product Demo is also provided
SM displays Sprint Board in Jira and the Team agrees/disagrees if the work described by User Story was completed
Through discussion, PO accepts/declines each User Story
If the User Stories contain a Minimally Marketable Product , then the Team show
Through discussion, PO accepts/declines the product
January 10, 2019

20. Sprint Retrospective Prior to the meeting: During the meeting:
The Sprint is completed
SM develops fun and interactive game that helps the team improve
During the meeting:
Participants: PO, SM, and the Team
Length: up to 4 hours
Through game participation, SM encourages the Team to improve itself, its product and processes
The Team identifies areas of improvement to which SM will track progress at the next Sprint Retrospectives
January 10, 2019

21. Scrum methodology
January 10, 2019

22. User Story Template
“As a <some persona>, I want <some business value>, so that <some business value or Justification>”
Use SMART goals when writing User Story:
Specific
Measurable
Achievable
Relevant
Time-bound
January 10, 2019

23. Introduction of New feature
Agile Roadmap
Project Title or Product Name
1st Quarter
2nd Quarter
3rd Quarter
4th Quarter
Goals
Product Introduction
Introduction of New feature
Cost reduction
Planning
This is a sample text. Replace it by your own text.
This is a sample text. Replace it by your own text. This is a sample text. Replace it by your own text. This is a sample text. Replace it by your own text.
This is a sample text. Replace it by your own text.
Marketing
This is a sample text. Replace it by your own text. This is a sample text. Replace it by your own text.
This is a sample text. Replace it by your own text.
This is a sample text. Replace it by your own text.
R & D
This is a sample text. Replace it by your own text.
This is a sample text. Replace it by your own text. This is a sample text. Replace it by your own text.
This is a sample text. Replace it by your own text. This is a sample text. Replace it by your own text.
January 10, 2019

24. Factors of a successful Agile project
The firm keeps established Agile methodology
The organization possesses a tool fitted for the project that helps in managing a project (Jira, MS Project Agile, or another Agile tool)
The Team understands, accepts, and follows the methodology
The project’s team has committed following personas:
Product Owner
Scrum Master
The Team
January 10, 2019

25. Dictionary
Start today - build your own
January 10, 2019