• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Agile Adoption and Initiation
 

Agile Adoption and Initiation

on

  • 1,795 views

 

Statistics

Views

Total Views
1,795
Views on SlideShare
1,795
Embed Views
0

Actions

Likes
0
Downloads
44
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

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
  • RegJacinta Intro Notes:KPMG in IT Advisory – Various roles such as process reengineering, Business Analyst, Project QA, various industries, USA-Contracted as a BA in ANZ Mortgages – Implemented Change control processes, Mentored Business Analysts, Project Inceptions, NZ and AustraliaSensis – Agile Development practices, White Pages BA, Online and Mobiles. Took several projects from Idea to implementation.Me Bank – Managing a team of 11 Business Analysts. Improving BA Practices, Building competency, Potentially Agile adoption
  • RegAgile Values and PracticesCommunicationStand upsCo located teamFeedbackRetrospectivesContinuous integrationAutomated testingCourageBig visible chartsAdaptive PlanningSimplicityIncremental designJust enough docoRe-factoringRespect-Pairing-Self organising team
  • RegCustomers Satisfaction:- How often have you designed a system to implement it 6 – 12 months later and the market has changed and you now want something differentReduce risk by:Getting Feedback early. Stakeholders see what you have implemented and may change their mindTesting a feature in production and get feedback from real usersContinuous Improvement:Feedback from users/ customers as well asContinually improve your processes
  • Reg
  • Reg
  • Reg
  • RegTalent - Team throw to Jacinta
  • Reg
  • jacinta
  • Reg
  • Reg
  • Reg
  • JacintaThe inception is about getting everyone on the same page, setting clear objectives and measurable goals.It’s the lack of clear objective that contribute to the project failure.Clear objectives means easier decision making.How big should it be:That depends on how much you know before your inceptionYou may just validate already understood vision and objectives
  • Jacinta
  • Use this slide or the one after
  • You will do several rounds of prioritisation and estimationE.g. Prioritise Epics, break down the must have’s into stories, then estimate storiesThen prioritise the stories within the epics
  • You will do several rounds of estimationE.g. Prioritise Epics, break down the must have’s into stories, then estimate storiesThen prioritise the stories within the epics
  • Jacinta

Agile Adoption and Initiation Agile Adoption and Initiation Presentation Transcript

  • Agile Adoption and Initiation
    Inception and Preparation
    Setting up for success… or failure…
    Reginald de Silva & Jacinta Streat
  • Introduction
    Who are we and why are we here:
    Reg
    Jacinta
    What we will be covering
    What is Agile
    Agile adoption – Why would you and How to?
    Pitfalls, risks and smells
    The Agile Inception – Objectives and tools
    What’s next…
  • What is Agile?
    Agile is an umbrella term for several iterative and incremental software development methodologies including Extreme Programming (XP), Scrum, Kanbanand Lean.
    Agile is:
    Customer-centric, rigorous and disciplined.
    Involves working in small iterations with concurrent analysis, development and testing.
    Focuses on empowering people to collaborate and make decisions together quickly and effectively.
  • Agile Adoption – Benefits of Agile
    Deliver business value
    Highest value first
    Early ROI (MVP – Minimum viable product, MMFs – Minimum marketable features)
    Customer satisfaction
    Reduce Risk
    Continuous Improvement
    Inspect & Adapt
    PDCA – plan, do, check, act
    Diagram by Karn G. Bulsuk (http://blog.bulsuk.com)
  • Agile Adoption – Benefits of Agile
    http://www.versionone.com/Agile101/Agile_Benefits.asp
  • Agile Adoption – Success
  • Agile Adoption – Success
    Perceived Project Success Rates
    Note: Accurate to within +/-7%
    Figures don’t add to 100% due to use of “ranged options”
    Copyright 2010 Scott W. Ambler www.ambysoft.com/surveys/
  • Agile Adoption Key Criteria
    Agile Coach
    Helps to establish approach
    Transfers knowledge and aims to make themself redundant
    Business buy-in
    Top down
    Bottom up
    Business commitment
    Is the owner
    Empowered to make immediate decisions when required
    Talent
    Right people in the right roles
    Right mindset
    Values and behaviours - Communication, Feedback, Courage, Simplicity, Respect
    Pilot Project
    benign way to adopt agile
  • How to Adopt Agile
    Ensure that proper change management is in place
    a structured approach to transitioning individuals, teams, and the organisation from a current state to a desired future state
    Solicit buy-in and commitment at all levels
    Select the right project
    Run an inception
    Involve the right people
    Build the team
    Establish a Framework
    What a sprint/iteration looks like
    What other processes are used
    Produce a backlog
    Sprint/Iteration 0
    Start building
  • Agile Smells
    Smells like success
    The team are engaged and confident
    The business partner is an advocate
    The first release is a minimum viable product
    Smells like failure
    The business partner is not accountable or empowered to make decisions
    Some team members are not on board
    Leadership is “command and control” rather than “servant leadership”
    The coaches and Agile leaders have never actually delivered an Agile project
    The project is not fun
    Agile adoption is being run by Project Managers
  • Business Partnership
    Business role:
    Is a member of the team
    Owns the project scope and delivery
    Is empowered to make decisions
    Manages the wider stakeholder group
  • Project Managers
    Traditional Project Managers do not belong in Agile projects.
    “Agile Project Management Responsibilities
    Most agile processes—and Scrum in particular—do not include a role called “project manager.” Without a specific person tasked with performing all managing duties, those responsibilities are distributed among the other roles on the project, namely the team, the ScrumMaster, and the Product Owner.”
    Mike Cohn
    http://www.mountaingoatsoftware.com/topics/agile-project-management
  • Project Managers cont…
    Agile is often perceived to threaten the very existence of Project Managers
    If you must have a traditional Project Manager then:
    Their role is to shield the team from external influences i.e. Manage upwards and across
    Get their buy-in– e.g. take steps to build their trust and confidence
    You may need to manage their expectations
    If your PMO does not support Agile then add that level of support or consider rebuilding your PMO
  • The Agile Inception
    Objectives:
    Set clear direction
    Set the project up for success
    Start work quickly
  • Define the Problem / Opportunity
    Where are we now?
    Where do we want to be?
  • Project Vision: Elevator Pitch
    For Australian based customers
    who require trans-Tasman payment solution
    the TBA
    is a Payments outsourcing solution
    that is flexible, secure & cost effective
    unlike ABC Bank File
    our product offers International Payments, NZ/AU functionality, RTC, UC & bulk cheque printing
  • Objectives
  • Trade off Sliders
  • Ropes and Fuels
  • Apple tablet
    User can see addresses, phone numbers
    IN
    Advertiser & User reporting
    User can add addresses
    User can save specific part of the captions
    Full Access to data via Search API
    New Products
    New Reporting channels
    Let users create lists
    User Testing Design and Usability testing
    Objectives measurement to be integrated across channels
    Accessibility Testing
    URL Redirect (device specific)
    Detailed customer profiling
    search result re-ordering (Relevance)
    Omniture Usage Stats
    Users should be able to search by Business Names
    Print. No changes to the way we print WP books
    Performance (same)/ not worse
    Change to data presentation
    content from external parties
    Better search experience
    Social Networking tools
    Syndicating Res data to non WP branded properties
    Team process improvements
    Data mining prevention
    Connect Business to users in new ways
    ‘Maverick’ factor; users generating new use cases
    Single search field on widget or other search types
    Access to all Bus & Gov data via search API
    Become more relevant to young users
    Better understanding of our data
    Less Ad banners
    Single search WPOL
    Protect the site from data mining
    User access blocking after misuse (API)
    Converting occasional users to frequent users
    Content Acquisition strategy initiative
    Content share to improve data quality & search!
    Using API for Location
    Better integration with digital only advertisers
    Maybe
    OUT
  • As Is/ To Be Process
  • Define Epics then Stories
  • Stories
    Epics
    Want to display banner advertising
    Want to display banner advertising based on the users previous search
    Want to display banner advertising targeting the users location
    Want to display banner advertising targeting the users location
    Want to be able to report on the performance of banner advertising
    Want a report showing performance by location
  • Prioritise Stories
    MoSCoW
    Must have
    Should have
    Could have
    Won’t/Wish to have
  • Estimation
    Examples:
    T-shirt sizes:
    Estimation for each Epic
    Large – 1 pair for a Release
    Medium – 1 Pair for 1 Iteration
    Small – 1 Pair for ½ Iteration
    Or
    Fibonacci sequence:
    Estimation for each Story
    Points, 1, 2, 3, 5, 8, 13, etc
  • Release Planning
    Release Plan at Epic Level then Story level
    Release Planning with Poker chips
    http://hillside.net/plop/2007/papers/PLoP2007_Yip.pdf
  • Retrospective
  • Iteration 0
    Test the process
    Project Planning
    Release planning
    Iteration planning
    Prepare environments
    Prepare Iteration 1 stories
  • What’s next
    Start building
    http://assets.scrumfoundation.com/downloads/1/scrumprimer121.pdf?1294640838
  • Questions?
  • References
    http://www.ambysoft.com/surveys/
    http://agilepainrelief.com/notesfromatooluser/2008/06/agilescrum-smells.html
    http://blog.bulsuk.com
    http://www.craiglarman.com/wiki/index.php?title=Image:Agile_and_iterative_1e.jpg
    http://en.wikipedia.org/wiki/Change_management
    http://hillside.net/plop/2007/papers/PLoP2007_Yip.pdf
    http://www.infoq.com/news/2008/05/agile-adoption-survey-2008
    http://www.mountaingoatsoftware.com/books/1-agile-estimating-and-planninghttp://www.mountaingoatsoftware.com/topics/agile-project-management
    http://www.mountaingoatsoftware.com/topics/planning-poker
    http://www.mountaingoatsoftware.com/scrum
    http://www.scrumalliance.org
    http://www.versionone.com/Agile101/Agile_Benefits.asp
    http://wikieducator.org/images/f/f1/Fibonacci.png
    http://icons.mysitemyway.com/wp-content/gallery/matte-white-square-icons-people-things/125544-matte-white-square-icon-people-things-shirt1.png
    http://upload.wikimedia.org/wikipedia/commons/thumb/b/b3/Aiga_elevator.svg/578px-Aiga_elevator.svg.png
    http://assets.scrumfoundation.com/downloads/1/scrumprimer121.pdf?1294640838
    Contacts:
    Reg de Silva http://au.linkedin.com/in/regdesilva
    Jacinta Streathttp://au.linkedin.com/in/jacintastreat