Agile methodology and JIRA Agile

1. Peter Perger
Ennosol Technology
JIRA Agile
Atlassian

2. Agile methodology
Scrum
Atlassian
JIRA
JIRA Agile
Workflow
Next

3. Agile methodology

14. Scope
(functionality)
Quality
Resources
(cost)
Schedule
(time)
Iron Triangle
Project Management

15. Technical Debt
bugs, bugs, bugs
spaghetti code
test automation
documentation
unreadable
complexity
stress

17. 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.
Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler,
James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C.
Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas
http://www.agilemanifesto.org

18. Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.
Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
Business people and developers must work
together daily throughout the project.
Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.
The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain 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 accordingly.
Principles behind the Agile Manifesto
http://www.agilemanifesto.org

19. Scrum

21. 1993
Framework
The New Product Development Game
Scrum Guide
Transparency
Inspection
Adaptation
Scrum Team
Product Owner
Development Team
Scrum Master
Scrum Events
Sprint
Daily Scrum
Review
Retrospective
Artifacts
Product Backlog
Sprint Backlog
Increment

22. Definition of "Done"
As Scrum Teams work together using the Scrum framework to develop a product, it is important for
stakeholders and Scrum Teams to understand when a product Increment can be called "Done." This
means that before a piece of functionality is in a potentially releasable state, it must adhere to a
common understanding of completion by those working on the Increment. Having a clear Definition
of Done helps Scrum Teams work together more collaboratively, increases transparency, and
ultimately results in the development of consistently higher quality software.
The Scrum Guide describes the Definition of "Done" as a tool for bringing
transparency to the work a Scrum Team is performing.
It is related more to the quality of a product, rather than its functionality.

23. "Scrum is so simple to understand but hard to execute"
"Scrum is lightweight, simple to understand (but)
extremely difficult to master"
"Scrum are easy to understand but hard to use"

25. Atlassian

26. Software Development and
Collaboration Tools
Dream big, work smart,
deliver fast
Software to plan, collaborate, code, and service.
Built for teams.

27. History
2002 | Scott Farquhar and Mike Cannon-Brookes | Australia | JIRA
13 Years
Founded in 2002
8 Offices
in 6 different countries
15 Products
in our arsenal
1,100+ Employees
and growing daily
40,000 Customers
Using our products
200+ T-shirts
Designed & worn
$20 mill. Donated
in Community licenses
107 User Groups
discussing our products over pizza and beer
2 Planets
With our software on them
1% Donated
of all profit, employee time, and equity
2.5 Corgis
Millie, Dawn, and Jupiter's a half Corgi
2 Robots
created with our software

28. IHMC Robotics, Tesla Motors, and Cochlear

29. Products
Track and support
JIRA
Plan, track, work
JIRA Service Desk
Service and support
Collaborate
Confluence
Create & collaborate
Confluence Questions
Share knowledge
Code
Bitbucket
Git & Mercurial code hosting
Stash
Git repository management
Solutions
Git Essentials
Complete development traceability
Agile Ready
Great planning, great software
Chat
HipChat
Chat and share
Dev Tools
Bamboo, FishEye,
Crucible, SourceTree...
Code quality
Add-ons
Agile, Portfolio, Capture,
Team Calendars...
Add-ons
More
Crowd, Enterprise,
University, Training...
Products, Services, Training

30. JIRA Agile

31. Track all the things!

32. What is JIRA
Prioritize, assign, track, report, audit issues
Extensible, customizable
Improves productivity, quality
Product management, Developers, Support
Workflows

33. Story, task, bug

34. E-mail
• Notification from all action (customizable)
• Reports by filters, daily report
• New issue by e-mail with fix format
• JIRA email this issue add-ons (Meta-Inf)

36. Backlog

37. Filters
Scrum board
Backlog
Issues
JQL
Filters
Rank
Priority

38. Scrum board

39. Custom boards
• Private boards
• Default filter
• Custom columns, statuses
• Swimlanes (strory, epic, assignees)
• Filters for board
• Colors (issue type, priority, assigness)
• Card layout (scrum board issues)
• Estimation type, time tracking
• Time zone, working days
• Issue detail view with custom fields
Different boards for every part of workflow
- tervezés, kivitelezés, tesztelés, kiadás -

40. Burndown chart
A Burndown Chart shows the actual and estimated amount of work to be done in a sprint

41. Velocity chart
The Velocity Chart shows the amount of value delivered in each sprint

42. Workflows

43. JIRA Workflow

44. The workflow determines which statuses are available.

45. Next

46. Time in issue management
Efficient workflow
Confluence
Github
Dig deeper into the JIRA

47. &
peter.perger
@
ennosol.eu
Q A