Scribd Logo
Upload

Welcome to Scribd!

  • 1 views

    BI Agile Approach

    Uploaded by

    Sdhffj Skafkdf

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    BI Agile Approach

    Uploaded by

    Sdhffj Skafkdf
    1 views9 pages

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    1 views9 pages

    BI Agile Approach

    Uploaded by

    Sdhffj Skafkdf

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    You are on page 1of 9

    Why Agile?

    Proprietary Information
    How do we approach Agile development?
    Agile Fundamentals
    • Face to face
    • Solving problems creatively
    • Business involvement from concept to completion
    • Reduced time to market
    • Early initial deliverables and quick wins to get
    feedback fast
    • Fast incremental build of small enhancement –
    keep it fresh
    • Flexibility and responsiveness to change
    • Ability to change focus to stay ahead of the game
    • User and customers needs at the heart of
    decision making
    • Shipping the product is everything Lean Principles
    • Optimise the whole
    • Eliminate waste
    • Empowerment to take decisions • Build quality in
    • Clear roles and responsibilities • Learn constantly
    • Power in the union • Deliver fast
    • Engage
    • High energy and positive vibe • Keep getting better
    • Better results • Ship early and frequently
    • Change is embraced
    Proprietary Information
    Scrum - Approach

    Proprietary Information
    Start up and running the process
    Initial Scoping – Sprint 0
    • Vision
    • Value
    • Build the scrum
    • Make all work visible - product backlog
    - Feature groups / Epics
    - User stories / tasks
    - Prioritise
    - Define the first delivery – Sprint 1
    - User stories
    - Acceptance criteria
    - T shirt sizing of User Stories
    - Minimum viable product
    • Risks and mitigations

    Proprietary Information
    Artefacts
    Kanban board shows scope and
    • Kanban status of individual items
    … rather than progress report
    • Burndown chart
    • Product backlog
    - Personas
    - Feature groups
    - Epics
    - User stories
    Burn Down Chart shows
    - Tasks progress
    … rather than a project plan
    • Sprint backlog
    • Impediments log
    • Learning log

    • + the Risk log (often not referred to in Scrum)

    Proprietary Information
    Ceremonies
    • Daily stand up
    - What has been done, what will be done, impediments

    • Retrospective
    - What went well, what could be improved
    - => updated ways of working

    • Sprint planning
    - Pulling user stories into the sprint based on priority
    - Refining the backlog
    - Detailing acceptance criteria

    • Product review
    - Product meets customer needs - Functionality, quality,
    usability
    - It is the right quality (eg standards, maintainability etc)
    - … eg A demo, a quality walkthrough

    Proprietary Information
    Roles - The Scrum a self organising team

    • Organiser / enabler
    • Servant / leader
    Scrum •
    Master Process guardian
    • Remove impediments to
    progress

    Users
    • Business Decision maker
    Product • Scope and delivery

    SCRUM Owner • Represent stakeholders


    fairly
    Stake
    Comprises of… holders

    • The team
    • Complete backlog items
    Team • Judge capacity
    Members • Estimate
    • Pull backlog items into
    the sprint

    Proprietary Information
    The Development Process is kept to a minimum
    • Scope and remit – The vision and sprint objective
    • Risks & Issues (Impediments)
    • Requirements – The Product backlog
    • Sprint backlogs + burn down
    • Self documenting software
    • System Documentation lite
    - Functional spec and basic documentation released fully at the end
    • Test plan and test results
    • Training materials as required

    • Flexible Change Management – just another backlog item that gets


    prioritised

    • Light touch governance – Production release only

    Proprietary Information
    Setting up Agile for success

    • Budget to execute
    • Education of the Product Owner / Stakeholders in the Agile ways of working
    - Team must be empowered to make all decisions
    - Team is democratic and cannot work in an autocratic environment
    - Product Owner must have high availability to the team (ideally full time; min 2d per
    week)
    • Build the right team
    - Skills, team behaviours, knowledge
    - Multi skilled T shaped people
    • Full time and Face to face
    - One location for the Scrum
    - No distractions – eg support work, other projects, department meetings – all must be
    kept minimal
    • The team has everything it needs to do the job - no interdependencies on Ecosystem
    partners or other teams
    • The team support the product, and no support handover is required
    • Governance is kept internal to the team – architect / quality role
    • A stable operational IT platform and toolset

    Proprietary Information

    You might also like