• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Agile for all
 

Agile for all

on

  • 2,252 views

I did a session with this topic at UXcamp Europe 2013.

I did a session with this topic at UXcamp Europe 2013.

Statistics

Views

Total Views
2,252
Views on SlideShare
1,029
Embed Views
1,223

Actions

Likes
1
Downloads
10
Comments
0

10 Embeds 1,223

http://www.scoop.it 520
http://blog.kvasnickajan.cz 470
http://zva.preview.bergisch-media.de 91
http://www.dp1-l.zva0.cluster.iquer.net 63
http://eventifier.co 40
https://twitter.com 20
http://www.dp1-s.zva0.cluster.iquer.net 15
http://eventifier.com 2
http://translate.googleusercontent.com 1
http://webcache.googleusercontent.com 1
More...

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Agile for all Agile for all Presentation Transcript

    • Copyright © 2006-13 The FatDUX, Cologne, GermanyAGILE FOR ALLUXcamp Europe 2013Senior UX Designervs Product OwnerStefan Böhland@spy23
    • LET YOUR CLIENTS BENEFITFROM AGILE DEVELOPMENTMETHODS AND KNOW HOW TODO THE UX IN SUCH A PROJECT
    • Why we went agileFix launch date+ Fix budget+ Flexible scope--------------------------= SCRUM project
    • HOW IS IT TO BE A PRODUCTOWNER?
    • Product Owner vs. UX DesignerProductOwnerUXDesignContent responsibilityIdeationProject controllingTeam coordinationReports and presentationsMarket- andcompetitor analysis
    • UX METHODS YOU CAN USEAS A PRODUCT OWNERSprint 0
    • Product backlog developmentScenarios PersonasCustomerJourneysEpics &Stories Priorisation
    • ScenariosTool: wufoo.com
    • Personas
    • Customer Journey
    • Epics & Stories
    • Epics & Stories
    • Epics & Stories
    • Epics & Stories
    • Story prioritization Business value with MoSCoW method Customer preference with Kano modelKampagnen
    • Story prioritization Business value with MoSCoW method Customer preference with Kano modelKampagnen
    • Prioritized Product Backlog
    • SCRUM SPRINTS
    • Sprint 1 – Basics and news
    • Sprint 2 – Knowledge template
    • Sprint 3 – Campaigns
    • Sprint 4 – Profiles
    • Sprint 5 – Search
    • BENEFITS THE SPONSORGETS
    • Velocity We have developed a new portal in just 14weeks With Scrum you can be as fast as twice thespeed of waterfall projects Launch date guarantee, but no scopeguarantee ;)
    • Flexibility Change the scope without change requests Dependencies to 3rd party service providers areeasier to manage
    • Quality The Scrum team feels responsible Quality remains a team factor from start untilthe project ends
    • Transparency Due to the restrict time boxing Scrum behalveslike a good project plan Sprint Review Meetings with product demos arelike milestones Your client is able to speak to the team duringeach product demo The client can talk to the product owner at anytime
    • WHAT WE HAVE LEARNEDTake-away
    • UX and Scrum Be creative but do as much as possible insprint 0 Three options for UX during Scrum sprits Integrated UX sprint Shifted UX sprint Hybrid UX sprint
    • UX and ScrumIntegrated UX sprintUX sprint nUXDEVSprint n Sprint n+1DEV sprint nUX sprint n+1DEV sprint n+1The integrated UX sprint is hard. It puts UX under pressure at the beginningof each sprint and DEV at the end.
    • UX and ScrumShifted UX sprintUX sprint n+1UXDEVSprint n Sprint n+1DEV sprint nUX sprint n+2DEV sprint n+1UX runs ahead of DEV by the length of one sprint. This looks and feels like asmall waterfall. More design artifacts may be created than necessary but thePO gets a chance to get approvals from stakeholders before DEV starts. Theteam is working on different stories at the same time which is not optimum forfinding the best solution together.
    • UX and ScrumHybrid UX sprintUX sprint n+1UXDEVSprint n Sprint n+1DEV sprint nUX sprint n+2DEV sprint n+1We suggest you to try hybrid UX sprints. During the first half of each sprintUX and DEV are working together on the same stories. During the secondhalf of the sprint the PO and UX prepare concepts for the planning meetingof the next sprint, do user tests and so on.UX sprint n UX sprint n+1
    • Team room Even if the Scrum project is not the only projectthe team members are working for Reduces setup times and context switches Boosts team communication
    • Experienced team members Junior teams may have problems to handletheir degree of freedom The product vision needs to be clear Hard acceptance criteria for each story arehelpful What’s not written in the story doesn’t belong tothe story. Thus it doesn’t need to be done ;)
    • More small stories A story shouldn’t be larger than the teamvelocity.
    • Your backlog is your backlog In our customer journey workshop we havecollected more than 100 stories. During theproject we have finished a quarter of them.
    • Thank you!Stefan Böhland@spy23slideshare.net/spy23