Payment Gateway Testing Simplified_ A Step-by-Step Guide for Beginners.pdf
Kevin burns are you collaborating enough-
1. Kevin Burns of DevJam
Are you collaborating
enough?
Scrum Day Twin Cities 2015
2. Kevin Burns of DevJam
Manifesto for Agile Software Development
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
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.
http://agilemanifesto.org/
3. Principles Are Your Guide
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 & developers must work together daily throughout project.
5. Build projects around motivated individuals. Give them the environment and support they need, and
trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team
is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, & users should be
able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence & good design enhances agility.
10. Simplicity--the art of maximizing the amount of work not done--is essential.
11. The best architectures, reqs, & 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.
http://agilemanifesto.org/principles.html Kevin Burns of DevJam
4. Kevin Burns of DevJam
Definition of Collaboration
Collaboration is working with others to do a task and to achieve shared goals. It
is a recursive[1] process where two or more people or organizations work together
to realize shared goals.
https://en.wikipedia.org/wiki/Collaboration
Noun: cooperation
Synonyms: association, collusion, combination, concert, participation, partnership, teamwork, alliance, fraternization, joint
effort, working together
Antonyms: disunion, division, separation, noncooperation
http://www.thesaurus.com/browse/collaboration
6. Chartering ( the project story )
Name and Timeframe
Elevator Pitch / Value Statement
Goals - Success Measures
Community Mapping
Working Agreements
Strengths - Constraints
Cadence - Logistics
Kevin Burns of DevJam
11. Quality is achieved through Collaboration
Customer/
PO/BA
Tester
Software
Engineer
Quality
Kevin Burns of DevJam
12. Scrum Ceremonies are Collaborations
Planning
Daily Standups
Review/Demos
Retros
It’s about meaningful conversations.
Kevin Burns of DevJam
13. Let’s play a Q&A game
How many of you think you’re collaborating enough?
How much is enough?
Kevin Burns of DevJam
If you’re not collaborating enough, what can you do
to collaborate more?
14. Let’s play a Q&A game cont...
Are we delighting our customers or simply meeting
their expectations (or worse)?
Is the customer accepting stories mid-sprint or
waiting until the end of the sprint?
What percent of stories are planned but not accepted
during the sprint?
Kevin Burns of DevJam
15. Let’s play a Q&A game cont...
Kevin Burns of DevJam
How predictable is your throughput?
Can your customer plan effectively based on your
throughput?
