PIPT – Mid Point Presentation
Upcoming SlideShare
Loading in...5
×
 

PIPT – Mid Point Presentation

on

  • 821 views

Team Amethyst's MPP on PIPT

Team Amethyst's MPP on PIPT

Statistics

Views

Total Views
821
Views on SlideShare
820
Embed Views
1

Actions

Likes
0
Downloads
2
Comments
0

1 Embed 1

http://www.slideshare.net 1

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

PIPT – Mid Point Presentation PIPT – Mid Point Presentation Presentation Transcript

  • Team Amethyst Achint Sethi Gulsharan Goraya Sai S Chandrasekharan Saravanakumar Mariappan You Imagine. We Create.
    • Project Overview
    • Team Overview
    • Goals
    • The story so far
    • What was good?
    • Plan for the future
    • Lessons Learnt
    June 2, 2009 Team Amethyst
    • Client
      • School of Computer Science
      • Point of Contact – Walt Schearer , Associate Dean for Finance and Administration
    • Business Needs
      • A standardized tool to be used by all Business Managers for “Planning and tracking financial aspects of activities in research projects”
    • Mentors
      • John Robert, SEI
      • Mel Rosso-Llopart, ISR
    June 2, 2009 Team Amethyst
    • Project Roles
      • Team Lead, Process Manager – Sai
      • Requirements Manager – Achint
      • Client liaison – Gul
      • Risk Manager – Saravana
      • Configuration Control Board – Sai, Saravana
      • Architecture Board – Sai, Saravana
      • Technology Review Board – Achint, Gul
    • Process Roles
      • Scrum Masters – Sai, Saravana
      • Product Owners – Gul, Achint
    June 2, 2009 Team Amethyst
    • Project goals
      • Improve upon the lessons learnt from our previous project at SSN
    • Process goals
      • Use a “project oriented” process
      • Stick to the process
    • Team goals
      • Use team resources optimally
      • Deliver the product on time meeting the scope
    June 2, 2009 Team Amethyst
    • Process
    • Project Management
    • Architecture
    • Tasks
    • Data Analysis
    June 2, 2009 Team Amethyst
    • Initial thoughts
      • To follow an agile process
      • To take ideas from Scrum, XP
    • When can we do Scrum? (Lesson Learnt!)
      • When deliverable is Code
      • When we have sufficient domain knowledge
      • When we have a “stable” architecture
      • When we have sufficient technology expertise
    June 2, 2009 Team Amethyst
    • Underlying framework – Scrum methodology
    • Four phases
      • Initiation – 1.5 months
        • September 1 – October 14
        • Task driven approach
      • Stabilization – 2 months
        • October 15 – December 8; 4 sprints
      • Skill Mastery
        • December 15 – December 31
      • Implementation
        • January 1 – March 15; 5 sprints
    June 2, 2009 Team Amethyst
    • Initiation
      • Project Proposal Sign off
      • Meetings with client – understanding the business domain
    • Stabilization
      • 15 day iterations
      • Sprint Planning – Sprint goals, tasks
      • Execute Tasks
      • Stand up meetings
      • Website update
      • Sprint Retrospective
    June 2, 2009 Team Amethyst
    • Requirements - Product Backlog
      • Importance
      • Story
      • Estimated story points
      • How to Demo?
      • Built over time by Product Owners
    • Risks
      • Risk management at beginning of every sprint
      • Loop through ‘Identify, Analyze, Monitor, Control’
    • Configuration Management
      • Configuration Control - baselines
    June 2, 2009 Team Amethyst
    • Driven by business drivers and technical drivers
    • Formal Quality Attributes Elicitation (QAE)
    • Quality Attributes identified and prioritized by client
    Reference: Amethyst_NFR_v0.1 June 2, 2009 Team Amethyst Quality Attributes # of critical scenarios Usability 6 Performance 3 Security 4 Availability 1 Extensibility Not identified
    • Technology Drivers
    • Quality Attributes and Technology drivers led us to arrive at a tiered architecture on top of Eclipse rich client platform
    June 2, 2009 Team Amethyst Quality Attribute Focus of investigation Usability Rich Client Platform Extensibility High cohesion; Eclipse plug-in architecture Security Low coupling; Tiered Architecture
  • June 2, 2009 Team Amethyst A contains B All images courtesy http://www.hp.com PIPT Tool Business Manager Computer PIPT Tool Business Manager Laptop Data Database server at SCS Legend S/w Component Contextual Boundary JDBC Connector A B
  • Principal Investigator Planning Tool Eclipse Rich Client Platform Generic Workbench (Perspectives, Editors, Views) JFace SWT Optional Plug-ins (Help, Update etc.) Equinox OSGi Platform Runtime JVM OS Key Layer Module June 2, 2009 Team Amethyst Key <<presentation tier>> <<plugin>> <<plugin>> <<logic tier>> <<plugin>> <<data tier>> <<presentation tier>> <<logic tier>> <<data tier>> <<plugin>> Presentation tier Logic tier Data tier Plug-in
    • More focus was on -
      • Understanding Business Process
      • Understanding the entities and data Model
      • Mitigating Technology Risks
    • Focus on architecture was to understand the critical quality attribute scenarios
    • Architecture is still being stabilized
      • Architecture being integrated with business process
    June 2, 2009 Team Amethyst
  • June 2, 2009 Team Amethyst Task List How much we achieved Proposal Product Backlog Risk Management Business Process Model Architecture Data Model Eclipse RCP Training Use case model High level timeline Quality Requirements Configuration Management
  • June 2, 2009 Team Amethyst Task List How much we achieved Process Document Website maintenance Infrastructure setup – Wiki, IIS, SVN Technology Feasibility Study Proof of Concepts Quality Assurance Plan
  • June 2, 2009 Team Amethyst Sprint Burn down Analysis
    • Transparent task allocation
    • Tasks fixed at beginning of every sprint
      • More responsible
      • Easy to measure
    • Mitigated technology risks
    • Creating subject matter experts in –
      • Technology – Gul
      • Process – Sai
      • Requirements – Achint
      • Architecture – Saravana
    June 2, 2009 Team Amethyst
    • Skill Mastery Phase
      • Individual skill improvement
      • Create prototypes
    • Implementation Phase
      • 500 story points estimated in backlog ~ 1000 hours estimated
      • 5 sprints, 4 persons, 72 hours per person per sprint ~ 1440 hours available
      • We know how to deliver in 15 day iteration cycles
    June 2, 2009 Team Amethyst
    • Getting started
      • New team
    • Requirements
      • Down-scoping took more time than expected
      • Used all 4 resources for first few client meetings
    • Learnt how to conduct effective meetings
      • Reduced time in meetings over the sprints by time tracking
    • Process
      • Got carried away with Agile
      • Lifecycle was good. Intent was wrong.
    June 2, 2009 Team Amethyst
    • Knowledge Sharing
      • Training on Process, Eclipse RCP
    • Architecture
      • Focus of our development should have been more on architecture
      • We could have explored ACDM as it seems to be a good choice for our design process
    • Planning and Tracking
      • Focus was on Sprint specific goals; not on semester goals
      • Learnt the nuances of “Focus factor” and “Velocity”
    June 2, 2009 Team Amethyst
    • Sprints
      • Learnt how to estimate tasks in a sprint better
      • Learnt that tasks must be at a micro level in a sprint
      • Sprint retrospective was really helpful
    • Others
      • We do not have a Quality Assurance Plan defined but we want to go for test driven development during Implementation Phase
    June 2, 2009 Team Amethyst
    • QUESTIONS?
    June 2, 2009 Team Amethyst
  • Backup Slides
    • Product Owners
      • Requirements
      • Client interaction
      • Act as the bridge between the client and the team
    • Scrum Masters
      • Sprint Planning
      • Risk identification
    • Task owners
    June 2, 2009 Team Amethyst
    • Initiation
      • Project Proposal Sign off
      • Meetings with client – understanding the business domain
    • Stabilization
      • 15 day iterations
      • Sprint Planning – Sprint goals, tasks
      • Execute Tasks
      • Stand up meetings
      • Website update
      • Sprint Retrospective
    June 2, 2009 Team Amethyst
  • Business Manager PIPT Tool Business Manager (1 .. n) Forecasting Data Forecasts System External Entity X Y Data flows from X to Y Admin User info Dashboard design, LD design PTA Information Business Context June 2, 2009 Team Amethyst Developer Principal Investigator
  • PIPT Tool PIPT Tool Business Manager Computer Business Manager Laptop Data Database server at SCS All images courtesy http://www.hp.com Legend S/w Component Contextual Boundary JDBC Connector A B A contains B PIPT Physical Deployment View June 2, 2009 Team Amethyst
  • Legend S/w Component Physical Laptop A B Business Manager Machine A contains B PIPT Client Deployment View June 2, 2009 Team Amethyst
  • <<device>> Personal Laptop/Computer <<component>> Eclipse RCP <<component>> <<library>> jChart <<component>> <<plugin>> PIPT <<device>> Central DB Server <<component>> MySQL Key: UML Node 3 rd -Party Component <<component>> PIPT Component <<component>> PIP Tool Deployment View Open source libraries <<component>> June 2, 2009 Team Amethyst
  • PIPT Client-side Layered View Principal Investigator Planning Tool Eclipse Rich Client Platform Generic Workbench (Perspectives, Editors, Views) JFace SWT Optional Plug-ins (Help, Update etc.) jChart Plug-in Platform Runtime JVM OS Key Layer Module June 2, 2009 Team Amethyst
  • June 2, 2009 Team Amethyst Key <<presentation tier>> <<logic tier>> <<data tier>> <<presentation tier>> <<logic tier>> <<data tier>> Presentation tier Logic tier Data tier Plug-in <<plugin>> <<plugin>> <<plugin>> <<plugin>>
  • June 2, 2009 Team Amethyst Sprint Burn down Analysis
  • June 2, 2009 Team Amethyst
  • June 2, 2009 Team Amethyst
    • Follow the chosen approach and methodology and deviate minimally from the objectives and goals of each phase
    • To follow test driven development and deliver a defect free product
    • Deliver a working feature every sprint
    • Involve the client during every sprint to provide feedback
    • Help the users get acquainted with the new system easily
    • Improve our team skills
    June 2, 2009 Team Amethyst
    • Initial thoughts
      • To follow an agile process
      • To take ideas from Scrum, XP
    • When can we do Scrum? (Lesson Learnt!)
      • When deliverable is Code
      • When we have sufficient domain knowledge
      • When we have a “stable” architecture
      • When we have sufficient technology expertise
    • We cannot do Scrum until we achieve the above 4 goals
    June 2, 2009 Team Amethyst
    • Project Proposal including –
      • Finalized Scope
      • Process Document
      • Support Processes
        • Requirements Plan
        • Configuration Management Plan
      • Schedule
        • Estimated time
        • Timeline for deliverables
        • Deliverables
      • Roles
      • WBS
    • Setting up of infrastructure
      • SVN
      • Wiki
      • Project Management Tools – Zoho/ Ace Project
      • Bug tracking system
    • Requirements
      • Documented as User Stories
    • The broad level timeline for the development cycle from October to March, will involve mapping the features to the Sprints.
    •  
    •  
    •  
    June 2, 2009 Team Amethyst
    • At the end of the semester, during December, we wish to deliver –
    •   SRS in the form of Product Backlog
      • Using requirements elicitation techniques learnt in Managing Software Development and Methods course
    • High level design diagrams developed for tasks during the sprints
      • Using knowledge gained in Architecture course
    • Sprint backlog
    • Sprint plans for completed sprints and forthcoming sprint
      • Using skills learnt in Managing Software Development
    • Test Cases for each of the tasks
    • User feedback for sprint demos
    • Analysis of work done in terms of overall estimated velocity and actual velocity
      • Burn down charts for each sprint will be provided
      • Time sheets of each team member
      • Leveraging skills learnt in Measurements and Managing Software Development course.
    • Working features developed at end of each sprint 
    June 2, 2009 Team Amethyst
    • At the end of March, the additional deliverables will be –
      • Final product – which will consolidate all the features already delivered during the sprints and shown as a demo of all the features
      • User guide
      • Product Technical documentation
    June 2, 2009 Team Amethyst