Scribd Logo
Upload

Welcome to Scribd!

  • 52 views

    L1 - Project Lifecycles and Agile Approaches

    Uploaded by

    Nikku Singh
    This document provides information about an IT Projects and Programmes module, including: 1. The module leader and tutors contact details and availability. 2. An overview of the module including the weekly topics, learning outcomes, and assessments which include an in-class assignment and exam. 3. Details of the lecture and tutorial class times and locations. The document gives students the essential information about the people running the module, what will be covered each week, what students will be expected to learn, how they will be assessed, and where and when classes will take place.

    Copyright:

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

    L1 - Project Lifecycles and Agile Approaches

    Uploaded by

    Nikku Singh
    52 views24 pages
    This document provides information about an IT Projects and Programmes module, including: 1. The module leader and tutors contact details and availability. 2. An overview of the module including the weekly topics, learning outcomes, and assessments which include an in-class assignment and exam. 3. Details of the lecture and tutorial class times and locations. The document gives students the essential information about the people running the module, what will be covered each week, what students will be expected to learn, how they will be assessed, and where and when classes will take place.

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document provides information about an IT Projects and Programmes module, including: 1. The module leader and tutors contact details and availability. 2. An overview of the module including the weekly topics, learning outcomes, and assessments which include an in-class assignment and exam. 3. Details of the lecture and tutorial class times and locations. The document gives students the essential information about the people running the module, what will be covered each week, what students will be expected to learn, how they will be assessed, and where and when classes will take place.

    Copyright:

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

    L1 - Project Lifecycles and Agile Approaches

    Uploaded by

    Nikku Singh
    This document provides information about an IT Projects and Programmes module, including: 1. The module leader and tutors contact details and availability. 2. An overview of the module including the weekly topics, learning outcomes, and assessments which include an in-class assignment and exam. 3. Details of the lecture and tutorial class times and locations. The document gives students the essential information about the people running the module, what will be covered each week, what students will be expected to learn, how they will be assessed, and where and when classes will take place.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 24

    IT Projects &

    Programmes
    Module Leader: Dr Peggy Gregory
    Module Tutors: John King, Maduka Uwadi
    MODULE TUTORS
    Module Leader
    Peggy Gregory – ajgregory@uclan.ac.uk
    Peggy is your main contact. See availability details in Starfish
    and Blackboard
    Module Tutors
    John King – jking11@uclan.ac.uk
    Maduka Uwadi – mcuwadi@uclan.ac.uk
    Edd Cooke - AECook1@uclan.ac.uk
    Module overview
    1. 1 Feb Project Lifecycles & Approaches
    2. 8 Feb Scrum
    3. 15 Feb Agile Project Framework
    4. 22 Feb Stakeholders & Requirements
    5. 1 Mar Agile teamwork
    6. 8 Mar Scheduling & Time management
    7. 15 Mar Estimating
    8. 22 Mar Risk
    9. 12 Apr Quality & Maturity
    10. 19 Apr Revision
    LEARNING OUTCOMES
    1. Critically evaluate different IT project and programme
    lifecycles and frameworks.
    2. Describe and critically assess IT project and programme
    stages and processes
    3. Critically examine approaches to IT development planning,
    contracts, risk, quality & maturity
    4. Identify and evaluate appropriate approaches for team
    working and involving stakeholders
    ASSESSMENT
    2 assessments: Assignment and Exam weighted 30:70
    IN-CLASS ASSIGNMENT
    Wk 4 Hand out and assign groups and topics
    Wks 5-8 Class-based worksheets, submit each week
    Wk 10 Poster session, final assessment
    EXAM
    2 hour exam in May examination period
    CLASSES:
    LECTURE: 13:00-14:00 MONDAY
    TUTORIALS: 2 hours on TUESDAY –
    09:00-11:00 or 11:00-13:00 or 13:00-15:00
    KEEP LOOKING AT THE ONLINE TIMETABLE – IT
    MAY HAVE TO CHANGE IN THE FIRST FEW WEEKS
    IT Lifecycles & Approaches
    Waterfall and beyond
    Contents
    Project Lifecycles
    • Sequential
    • Iterative
    • Incremental
    • Hybrid
    Project Approaches
    • Plan-driven
    • Agile
    Sequential Model - waterfall
    requirements

    design

    code

    test

    deploy

    maintain
    Products From Each Stage
    Requirements gathering  Specification
    Design  Design detail – architecture, classes, DBS, UI
    Code  Code and documentation
    Test  Test cases, results
    Deploy  System running in live setting
    Maintain  New code, new tests, new documentation
    Sequential Model:
    Rationale & Assumptions
    Rationale
    • Logical approach
    • Supports job specialisms
    • Supports use of Project Manager to co-ordinate the whole
    • Can design UI, architecture and code in early stages and then
    implement
    Assumptions
    • Deliver everything at the end
    • Go through the process once
    • Nothing is going to change
    • Don’t need team work
    Iterative Model - Spiral
    Different Types of Iteration
    Evolutionary iteration (Spiral model)
    Build product gradually
    Start small and extend, with feedback
    Throw-away prototyping
    Fast development to confirm idea
    or build alternatives and choose
    Horizontal prototyping
    Broad view of whole system
    (overview)
    Vertical prototyping
    Prototype of a sub-system (feasibility)
    Iterative Model:
    Rationale & Assumptions
    Rationale
    • Reduce uncertainty about technical issues and client needs
    • Explore client/user needs through trial and error. Difficult to
    ‘imagine’ system up-front, pick up missing/changing requirements
    • Explore design and programming issues
    • Explore ‘look and feel’, look at alternatives
    Assumptions
    • Don’t need to deliver until it is complete
    • Don’t mind ‘wasting time’ on work that might get thrown away
    • Have access to client to review product
    Incremental Model – Frequent chunks
    Regular releases of developed software
    Jan Feb Mar

    Each increment contains requirements, design, code


    and test.
    May do in VERY frequent short bursts (daily, hourly)
    May have gaps between or small overlaps
    Jan Feb Mar
    Incremental - a product model
    Incremental Approach
    • Break product into segments or features
    • Deploy feature by feature to the end users
    • Ability to respond to changes as they happen
    • Ability to respond to pressure from competitors
    Incremental: Rationale &
    Assumptions
    Rationale
    • Early delivery of value to client
    • Early delivery of value to end-users
    • Early assessment of customer interest / value
    • Good for continuous delivery products such as websites
    Assumptions
    • Have to be able to deliver value in chunks
    • Need notion of MVP (minimum viable product)
    • Need access to customer use data to be able adapt and improve
    Hybrid Models
    Lifecycles may be mixed:
    Sequential used during Iterative
    for particular components i.e. database or hardware
    Sequential used during Incremental
    each short burst is a small waterfall
    Iteration used during Sequential
    to develop user interface/ test design ideas
    Incremental and Iterative used together
    Agile methods use this approach
    Overview
    Sequential linear development
    Iteration gradual development and prototyping
    Incremental regular releases of developed software
    Hybrid mixed development approaches
    Agile Methods
    Agile methods
    Agile methods for IT were first proposed in 2000, but the ideas
    had been around for years
    The Agile Manifesto was agreed at published in 2001 at a
    meeting between 17 software development consultants
    The Agile Manifesto summarises the values and principles of
    agile, but there are many different Agile methods, and most
    organisations that use them tailor them to their context
    Agile methods are also used outside IT and the idea of the
    Agile Enterprise has been around for longer than Agile IT.
    Agile Manifesto
    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
    https://agilemanifesto.org/
    TWELVE Agile Principles
    1. Early and continuous delivery 7. Working software is the primary
    software. measure of progress
    2. Changing requirements welcomed 8. Sustainable development
    3. Deliver working software 9. Technical excellence and good
    frequently design enhances agility
    4. Business people and developers 10.Simplicity is essential
    must work together daily
    throughout the project 11.The best architectures,
    requirements, and designs emerge
    5. Build projects around motivated from self-organizing teams
    individuals
    12.The team must reflect on how to
    6. Face-to-face conversation is become more effective regularly
    essential https://agilemanifesto.org/
    The problem with IT Projects

    You might also like