Upload
truongnga
View
225
Download
0
Embed Size (px)
Citation preview
Mastering our Agile Product
Today Workshop Plan
What is JIRA ?
What is Agile Methodology ?
What is JIRA Agile ?
What is ICEPAY Custom Setup ?
How Should I use It ?
Workshop !
What’s Next ?
Today Workshop Plan
What is JIRA ?
What is Agile Methodology ?
What is JIRA Agile ?
What is ICEPAY Custom Setup ?
How Should I use It ?
Workshop !
What’s Next ?
What is JIRA ?
It’s a Issue tracking product• Enter your bugs
• Assign the bugs
• Work on the bugs
• Release the bug fixes
Waterfall / V-Shaped cycle point of view• Looping workflow
• No precise ownership / or all
• No advanced reporting
• No modern performance review
Today Workshop Plan
What is JIRA ?
What is Agile Methodology ?
What is JIRA Agile ?
What is ICEPAY Custom Setup ?
How Should I use It ?
Workshop !
What’s Next ?
What is agile methodoly ?
Cross functional teams
Collaboration
Iterative / Incremental / Evolutionary
Face to face
Short Cycle
XP, Kanban, Scrum
What is agile methodoly ?
Today Workshop Plan
What is JIRA ?
What is Agile Methodology ?
What is JIRA Agile ?
What is ICEPAY Custom Setup ?
How Should I use It ?
Workshop !
What’s Next ?
What is JIRA Agile ?
An Element of a Software Suite done to organize in a Agile way our software creation, delivery and improvement
• Idea
• BugJIRA
•OrganizeJIRA Agile
•Documentation
•Specification
JIRA Confluence
•Code ManagementJIRA Bitbucket
•Code QualityJIRA Bamboo
•Customer SupportJIRA Service Desk
Today Workshop Plan
What is JIRA ?
What is Agile Methodology ?
What is JIRA Agile ?
What is ICEPAY Custom Setup ?
How Should I use It ?
Workshop !
What’s Next ?
ICEPAY Custom Setup - Vocabulary
Issue : An input• EPIC : One to rule them all• Story : That’s how to do it !• Bug : oops• Idea / Suggestion : while shaving this
morning I thought about this• ICE Merchant Request : This
merchant want that, and is entitled to it
Workflow : A process to handle an issue
• Status• Transition
Ticket• A wrote issue with a reference
A Sprint• A time unit of 10 open days
ICEPAY Custom Setup – Bugs & Merchant requests
ProductionICE In Production
ReviewICE Review
ReadyICE Ready for Release
TestingICE Testing
DevICE Development
Ready for ITICE Development Queue
OverviewICE Product Review
EvaluateICE Product Queue
SubmitICE Bug Queue / ICE Merchant Queue
ICEPAY Custom Setup – Idea / Suggestion
Evaluate
ICE Product Review
Submit
ICE Suggestion Queue
ICEPAY Custom Setup – Stories
ProductionICE In Production
ReviewICE Review
ReadyICE Ready for Release
TestingICE Testing
DevICE Development
Ready for ITICE Development Queue
OverviewICE Product Review
SubmitICE Product Queue
All Statuses
ICE Ready for production• When IT says “ok this
done”
ICE In production• When it’s Live and
customer have Agreed it fits the needs
Graveyard• When it’s not going to be
done
Bucket list• When it’s good to keep in
mind, but clearly not now
ICE Development• Nice ! Someone is
creating your Issue
ICE Testing• Groovy ! IT is testing if
the issue behavior is as expected
ICE Review• Awesome, Product & I
are validating the issue!
ICE Bug queue• When you’ve entered a bug
ICE Merchant queue• When you’ve entered a
merchant request
ICE Suggestion Queue• When you’ve entered a
suggestion
ICE product Queue• Taken in account, but no one is
on it
ICE Product Review• Product is working on your
issue
ICE Development Queue• Ready to be worked on by IT
Today Workshop Plan
What is JIRA ?
What is Agile Methodology ?
What is JIRA Agile ?
What is ICEPAY Custom Setup ?
How Should I use It ?
Workshop !
What’s Next ?
How should I use it – Who can do what ?
Create Bug• Everyone !
Create ICE Merchant Request• Everyone !
Create Idea / Suggestion• Everyone !
Create Story / epic• Agile Development
• Agile Manager
How should I use it – Fields explained
EPIC LINK : What your issue relates to• Everyone
Priority : How important you think it is• Everyone• Normally you should leave it to normal or downgrade it. • If it is important. Don’t wait. Come and talk to product right away.
Assignee : Who is in charge • Agile developer / Manager ONLY
ICE Employee reporter : Where you have to select who you are• Members with grouped accounts
How should I use it – Fields explained
ICE Sponsor : Who is following this issue• Everyone if applicable
ICE Tools : Which tools are impacted• Everyone
ICE Category : What type are we talking about• RUN : Day to day / bugs /
• Innovation : Idea / workaround….
Lucidchart : A modelisation / workflow• Agile developer / manager
How should I use it – Fields explained
Summary : top 10 words to explain• Everyone
Description : Be precise, give some examples• Everyone
Linked Issue : Type and relation• Everyone (be sure of what you are doing)
Attachment : Sources, screenshots, data, emails …• Everyone
How should I use it – Fields explained
TESTING / Test case : How are you going to check if the fix provided is working• Everyone
Today Workshop Plan
What is JIRA ?
What is Agile Methodology ?
What is JIRA Agile ?
What is ICEPAY Custom Setup ?
How Should I use It ?
Workshop !
What’s Next ?
Today Workshop Plan
What is JIRA ?
What is Agile Methodology ?
What is JIRA Agile ?
What is ICEPAY Custom Setup ?
How Should I use It ?
Workshop !
What’s Next ?
What’s Next ? - Roadmap
What’s Next ? – Step 1
[Currently] to September 7th : Phase 1 – The shacking boat• Length : 2 Cycles of 10 working days (2 weeks) -> 1 month• Description : In this phase things might get a bit disturbing for some of us, not
for long I hope !• Objectives
• Setting up custom process• Migrating from previous tools• Sharing knowledge on product and how to
• Events• Every 2 week : Monday Prioritizing• Workshops (4+)• Review event : How did YOU felt about this first cycle, what would YOU change ?
What’s Next ? – Step 2
From September 8th to October 19th : Phase 2 – Enjoying• Length : 3 Cycles of 10 working days (2 weeks) -> 1.5 month
• Description : We are starting to get use to things, let’s add some more !
• Objectives• Investing each team (Finance, Support, Sales, Marketing, Underwriting, Compliance)
With strong ownership of their issue
• Events• Having a formal reporting process : Every 2 weeks
• through a every 2 week review of their tickets
• Review event : How did YOU felt about this first cycle, what would YOU change ?
What’s Next ? – Step 3
From October 20th to November 30th : Phase 3 - Mastering• Length : 3 Cycles of 10 working days (2 weeks) -> 1.5 month
• Description : Dammed ! We are getting to good as this, let’s rock it !
• Objectives• Being able to have a reliable issue resolution planning
• Events• Review event : How did YOU felt about this first cycle, what would YOU change ?
What’s Next ? – Step 4
Phase 4 : Routine• By then we should be used to the following routing.
• D0 : Sprint planning – Priority Selection
• D1 : Reporting on previous sprint
• D4 : Ordering / evaluating pending issues (for next sprint)
• D9 : Team’s wish list (for next sprint)
• D10 : release
• D0 …