Agile Mindset P1

1. Be a servant leader to the team all the time

2. Empowering them and removing any impediments
3. Give them tools they need to succeed while staying out of their way
4. Engage PO to document the features, prioritize them in product backlog
5. Only PO can prioritize feature in product backlog
6. If PO refuse to do so because they feel everything is valuable, you must train them of doing so
(prioritize)
7. You DO NOT prioritize the features yourself, only PO can do

Agile Mindset P2

1. Use co-location
2. F2f communication with white board and markers are the best communication
3. Provide agile team with lots wall space so that they can write/use sticky notes

Agile Mindset P3

1. Information need to be radiated through use of large charts/graphs [burnup or burned down
chart]
2. Any problem in project should be resolved by project team, Let project team choose solution
while coach and support their solution
3. Provide safe environment for disagreement
4. Do no punish for opinion difference
5. Conflict is positive step and opportunity to learn

Agile Mindset P4

1. Try to limit work in progress through Kanban

2. Consistently communicate and re-communicate project vision to team
3. Understand needs of team members and find way to motivate them

Agile Mindset P5

1. Make sure people understand what failure and success look like on project
2. Be central figure to team, not dictator
3. Good ethical values

Agile Mindset P6

1. Review the methods work was completed by doing retrospective

2. Utilize feedback loops
3. Feedback loop occurs when you complete a task, get the lesson learn, use it as input into your
next task
Agile Manifesto

1. Individual & interaction over process & tools

2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan

Agile guiding principles

1. Highest priority to satisfy customer through early and continuous delivery of valuable software
2. Welcoming changing requirements even in late development. Agile harness change for
customer’s competitive advantage
3. Deliver working software frequently from couple of weeks to couple of months with preference
shorter timescale
4. Business people & developers must work together daily throughout project
5. Build project around motivated individuals, give them environment and support they need and
trust them to get job done
6. F2F is most efficient to convey information
7. Working software is primary measure of progress
8. Agile promote sustainable development
9. Continuous attention to technical excellence, good design enhances agility
10. Simplicity: art of maximizing amount of work not done is essential
11. Best architecture, requirements, designs emerge from self-organizing teams
12. At regular intervals, team reflects on how to become more effect and will do adjustment

Agile Terms

1. Product owner: customer on project

2. Agile PM: manage agile projects
3. Product backlog: project requirements from stakeholders
4. Sprint planning meeting: meeting done by agile team to determine what features will be done in
next sprint
5. Sprint backlog: work the team selects to get done in next sprint
6. Sprint review: inspection done at the end of sprint by customer
7. Retrospective: meeting done to determine what went wrong during the sprint and what went
right, lesson learned for the sprint
8. Customer/Product Owner writes product backlog (requirements)
9. Product backlog is prioritized by value/product owner
10. Product owner-product backlog-sprint planning meeting-sprint-spring backlog- sprint review
meeting-sprint retrospective

Scrum

1. Set of team guidance practice, roles event, artifacts and rules

2. Transparency, inspection and adaptation
 3. Product owner: own product vision, define features, prioritize features, can change features &
priorities
4. ScrumMaster: facilitator, focus team and protect from external interruption, look ways to
enhance productivity, assist product owner
5. Development team: small group with project skill, generate option for delivery, manage own
work, focus on steady delivery of high quality features

Scrum activities

1. Sprint planning meeting

 What work will be done in that sprint and how the work will be achieved
 Dev Team predicts what can be delivered based on estimates, project capacity, past
performance
 Determines how this functionality will be built and how team will organize to delivery
sprint goal
 Output is sprint backlog
2. Sprint
 Timeboxed
 Includes sprint planning meeting, daily scrum, actual work, sprint review meeting, sprint
retrospective
 No changes are made during sprint
 Development team members are kept same throughout the sprint
3. Daily scrum
 15 minute timeboxed
 Same time, same place
 What did you do yesterday?
 What will you do today?
 Any impediments in your way?
4. Sprint review
 Takes place at end of sprint
 To gather feedback from stakeholders on what team has completed in sprint
 Team demonstrates work that was completed during sprint
 Create conversation between team, stakeholders to make product better
5. Sprint retrospective
 Inspect, create a plan for improvement to be done in next sprint
 What went well, wrong, what to do more, what to do less
Scrum Artifacts

1. Product increment, product backlog, sprint backlog

2. Product backlog
 Prioritized list of all work that need to be done to complete a product
 Product owner prioritize, refined, groom backlog
3. Product increment
 Part of product done after sprint
 Done to get feedback after each sprint
 Product owner, team need to agree upon definition of done before team starts working
on product
4. Sprint backlog
 Set of items from product backlog that were selected for specific sprint
 Accompanied by plan of how to achieve the sprint goal
 Serves as development team forecast for functionality that is part of the sprint
 Highly visible view and updated by development team

Extreme Programming (XP)

1. Software development centric agile method

2. Focus software development good practices
3. Simplicity, Communication, Feedback, Courage, Respect

XP Roles

1. Coach
 Acts as mentor, guide process and help team stay on track, facilitator to help team
become effective
Customer
 Business representative who provide requirement, priorities and drives business
direction for project
Programmer
 Developer who build product
Tester
 Help customer define and write acceptance tests for user stories
XP Practices

1. Release planning
a. Push new functionality to production user
b. Customer outlines functionality required
2. Iteration planning
a. Short development cycles within a release (sprint)
b. At start is conducted
c. Customer explain functionality needed
d. Developers break functionality into tasks, estimate work
e. Based on estimate, amount of work accomplished in previous release
3. Small release
a. Frequent, small release to test environment
b. Demo progress, increase visibility
4. Customer test
a. Customer describes one/more test to show software is working
b. Builds automated test to prove software is working
5. Collective code ownership
a. Any pair of developers can improve, amend any code
b. Multiple people work on all code which results in increased visibility and knowledge of
code base
c. Leads to higher quality
d. Less risk if programmer leave, since knowledge is shared
6. Code standards
a. Follow consistent coding standard
b. Code looks as if it has been written by a single, knowledgeable programmer
7. Sustainable pace
a. Practice of maintaining of sustainable pace of development optimizes the delivery of
long-term value
8. Metaphor
b. Use metaphor and similes to explain design, create shared technical vision
c. These descriptions establish comparison that all stakeholder can understand on how
system work
9. Continuous integration
a. Integration involves bringing code together and make sure it all compiles and work
together
b. Critical because it brings problems to surface before more code is built on top of
faulty/incompatible designs
10. Test driven development [TDD]
a. Team writes tests prior to develop new code
b. If tests are working correctly, initial code that is entered will fail the test
c. The code will pass the once it is written correctly
11. Pair programming
a. Production code written by 2 developers working as a pair to write and provide real time
reviews of software as it emerges
 b. Helps spread knowledge about system through the team
12. Simple design
a. Code is always testable, browsable, understandable
13. Refactoring
a. Remove redundancy, eliminate unused functionality
b. Saves times, increase quality