Methodology

Card Set Information

Author:
bestassociate
ID:
16635
Filename:
Methodology
Updated:
2010-04-28 16:25:50
Tags:
PMBB
Folders:

Description:
Methodology
Show Answers:

Home > Flashcards > Print Preview

The flashcards below were created by user bestassociate on FreezingBlue Flashcards. What would you like to do?


  1. Project Initiation Activities?
    - Sliver Identified

    - Product Feature Demos

    - Knowledge Transfer

    - Operational Walk-Thru

    1
  2. Inception Phase includes what?
    - Define scope: Program, Project, Slivers

    - Business Requirements

    - Organize Int. Projects

    - Breakdown to Slivers

    - Identify Process Improvement

    - Capture High-Level Requirements, Use Cases, & Work Types

    2
  3. What is included in the Transition Phase?
    - Complete System Test

    - Ensure Solution is maintainable by IT (Including Support)

    3
  4. What are go-live activities?
    - Deploy final release candidate

    - Maintain app with enhancements, fixes, and change requests by IT and business users

    - Monitor System

    4
  5. What are the benefits of the Smart BPM approach?
    - ROI - business value realized sooner

    - Reuse is emphasized

    - Lessons learned applied

    5
  6. Plan for small releases:

    Target # of months?
    No longer than?
    - Target 3 month releases

    - No longer than 6 months

    6
  7. SmartBPM iteration recommendations include:
    - Target 3 month releases...no more than 6 months

    - Releases ideally will be self-contained

    - Maintenance patches between major releases

    - Prioritize most critical functionality and higher risk features in early releases to obtain maximum value and lower risk - re-prioritize after each release

    7
  8. SmartBPM Benefits
    - Short Release/ROI

    - Users provide higher quality requirements for later phase

    - Short release - less pressure for users to evaluate too much

    - Planning for multiple releases establishes framework for value gain

    8
  9. What is Pega Scrum?
    - Scrum using DCO tools - not a modification of Scrum

    • - Methodology is:
    • >Agile & Iterative
    • >Releases Capability quickly
    • >Focus on Value
    • >Documents at appropriate level
    • >Extensible = change by project

    9
  10. Pega Scrum stages - 1 of 2
    • - Vision Definition
    • >Big picture understanding
    • >Develop Roadmap & High Level Product Backlog

    • - Project Initiation
    • >Determine scope of R1
    • >Kick-Off
    • >Set Expectations

    • - Enterprise Planning
    • >Infrastructure
    • >Class Structure

    10
  11. Pega Scrum stages 2of2:
    • - Enterprise Planning
    • >Infrastructure designed/sized for all releases
    • >Class Structure support re-use

    • - Release Implementation
    • >Execute 1 release cycle targeted at the pre-defined product backlog

    • - Release Retrospective
    • >Continuous Improvement

    11
  12. Pega Scrum 5 Stages:
    • - Vision Definition
    • - Project Initiation
    • - Enterprise Planning
    • - Release Implementation
    • - Release Retrospective

    12
  13. Application Profiler (AP) Outputs Include:
    - Application Profile document

    - Project Sizing Worksheet (Timeline & more...)

    • - Work Object used by
    • >Application Accelerator
    • >Project Management Framework (PMF)

    - Used in Inception Phase

    13
  14. Application Accelerator Details:
    - Consumes Application Profile

    - Users expand on Scope, Work Type, Atomic use cases, actors, & more

    • - Creates rules for foundation
    • > Also creates its own Work Object

    - Used in Elaboration phase

    14
  15. Project Management Framework Details:
    - Assigns Tasks (Including group tasks)

    - Tracks Bugs

    - Tracks Issues

    - Used Anytime - Typically started in inception phase and so-on

    15
  16. Test Management Framework (TMF) Details:
    • - End-to-end testing of app
    • >Testing occurs in segments using flows in your app

    - Elaboration phase and so-on

    16
  17. Terminology: Objective
    - Project goals that when reached signify ROI/Benefits

    17
  18. Terminology: Requirement
    - Details of a business need

    - Used to verify results of App is what business needed

    • - Inventory of events, conditions, or functions
    • >Can be generic (e.g., screen render in under 2 secs.)
    • >Can articulate a business rule
    • >Should be used as success criteria
    • >Describe in non-technical terms

    18
  19. Terminology - Work Types
    • - Focal point for business
    • >Defines the info required to execute the process (insurance claim)

    - Typically derived from Business Rule Cases

    • - Inherits from one of the following:
    • >Work Object
    • >Work Cover
    • >Work Folder

    19
  20. Terminology - Business Use Case:
    - Describes Full Process Lifecycle

    - Generated by Business

    - NOT entered in DCO (Atomic use cases are instead)

    - Include Primary & Exception paths

    - Multi-Level: one use case can use functions of another

    20
  21. Business Use Case document includes:
    - High level description

    - Actors

    - Preconditions

    - Postconditions

    - Frequency of use

    - Normal course of events/and exception paths

    21
  22. Terminology - Atomic Use Cases:
    • - Describe part of business process
    • >Many atomic use cases in one business case

    • - Small & Granular - intered in DCO tools
    • >Support re-use

    - Do not change owner

    - Associated with one or more Work or Support Types

    • - Can be linked to rules
    • >Flow actions, harnesses, activities, screen flows, or flows

    22
  23. Key Objectives of Project Initiation:
    • - Prepare, organize, and set the proper expectations for the project
    • >POC
    • >Proof-of-Technologies
    • >Prototyping

    - Education: Enablement by role

    23
  24. Project Initiation Key Activities 1of2:
    • - Operational Walk-Through
    • >Identify/Review As-Is/Current State Review
    • >Process Improvement Begins

    • - Knowledge Transfer
    • >Demos, Docs, Workshops
    • >Enablement Training

    • - Identify & Organize
    • >Programs, Projects, & Slivers
    • >Staffing Models
    • >Milestones
    • >Risks/Assumptions

    24
  25. Project Initiation Key Activities 2of2:
    • - Organizing Releases
    • >Key Criteria
    • - Most Business Value
    • - Short Delivery Cycle
    • - Reduces Risk

    25
  26. Project Initiation - Key Deliverables & Roles:
    • - Deliverables
    • >POC
    • >Workshops
    • >Enablement Training
    • >Roadmap Planning

    • - Roles
    • >Business Sponsor
    • >Project Management
    • >SME's
    • >Supporting Technical Resources

    26
  27. Inception Phase Objectives:
    - Define scope of each development effort

    - Business Requirements detailed & organized in projects

    - Projects broken into slivers

    • - Application profile built from each sliver
    • >Scoping Doc Created
    • >Sizing Tool created

    27
  28. Inception Phase - Perform Operational Walk-Through Details:
    • - Walk Through current operaton and look for improvements
    • >Duration is Typically 1-3 Days
    • >Identify Quick Wins
    • >How is work completed - 6 R's (Received, Routed, Researched, Responded To, Resolved, Reported on)

    - Improve the Process

    • - Project Scope is defined/refined
    • >Direct capture capabilities

    28
  29. Define Roadmap, Project, Sliver:
    - Roadmap defines long-term product map and is broken down into projects

    - Projects define functionality or business processes for each project and prioritize the functionality

    - Slivers make up projects and are organized in releases and iterations. Slivers are made up of use case sets. Use case sets are made up of use cases.

    29
  30. Inception Ground Work
    • - Inventory what exists
    • >Analyze what current artifacts exist
    • - Including objectives, requirements, use cases, etc.
    • - Create inventory
    • >Analyze Artifact Details
    • - Workshops if necessary

    - Leverage work that has been done

    31
  31. What are Objectives used for?
    - Checklist for a successful application

    - Used at end of development to ensure business value

    32
  32. Requirements?
    >Begin with?
    >What can they be linked to in DCO?
    - Describe exactly what business wants

    • - Begin with:
    • "The system shall provide the capability to"

    - May be linked to UseCases in DCO.

    33
  33. What state are Use Cases during the inception phase?
    - High-Level (Detailed Later)

    • - Describe the process by which the requirements will be stepped through
    • >Paragraphs & Bullets

    34
  34. What state are use cases in during the inception phase?
    - High-Level (Detailed Later)

    • - Describe the process by which the requirements will be stepped through
    • >Paragraphs & Bullets

    34
  35. Inception Phase - Objectives, Requirements, Use Cases....Things to Note:
    - The level of detail is not full

    - Sentences short/to the point

    - Sentence fragments are good as long as clear

    - Statements referenced directly using Reference Numbers

    35
  36. CAP - Create Application Profile Process:
    - Pull data from Business Use Cases and enter in AP

    • - Collaboration to create AP & Sizing Tool
    • >3-5 Days

    36
  37. Inception Phase...Application Profile Provides:
    - Functionality to enable users to work individually on specific steps then merge

    - An understanding of scope and input to sizing tool

    - Complete AP includes: High Level, Description of Req's, Work Types, Use Cases, Interfaces, Reports & Correspondence

    37
  38. Inception Phase - Application Profile (Submit AP, Sizing Tool, For Review).

    Process for Review?
    - ROI is clearly articulated

    - Work Types/Use Caes adequately describe work

    - Timeframes & Staffing estimates are reasonable

    - High-Level design & frameworks provide adequate technical coverage

    38
  39. What are the 6 Inception Phase tools?
    • - Application Profiler (AP)
    • - Sizing Tool
    • - MS Project Plan Template
    • - Project Management Framework (PMF)
    • - Phase Readiness Checklist
    • - Methodology Alignment Workshop (MAW)

    39
  40. What are the 7 Inception Phase Roles?
    • - Business Sponsors
    • - PM's
    • - Business Analysts (BAs)_
    • - SMEs
    • - System Architect
    • - Testing Resources

    40
  41. What is a Methodology Alignment Workshop (MAW)?
    • - Blends a non-PRPC methodology with Build For Change aspects of SmartBPM
    • >Methodology in use is mandated by client
    • >MAW shows how to incorporate DCO capabilities into existing methodology

    - MAW demos SmartBPM and its best practices

    41
  42. What is Hybrid Methodology?
    - Understand Current Methodology

    - Solid understanding of SmartBPM

    - Both methodologies blended

    42
  43. What are the key steps in the Elaboration & Construction phase?
    - Run Application Accelerator

    - Accomplish DCO Sessions

    - Iterative Development

    43
  44. Environment setup planning: When does the environment need to be set up?
    - Before elaboration or Construction can take place environment must be set up.

    44
  45. What does the Environment Setup Services Workshop identify?
    • - Identifies business needs for application:
    • >Hardware/OS Allocation
    • >System Access (Internet, VPN, etc.)
    • >Backup/Recovery & Disaster Recovery
    • >SLA/Up-Time
    • >Performance, sizing, & capacity plan security
    • >Interfaces to other systems
    • >Review Technology Layer ownership
    • >Monitoring

    • 45
  46. Elaboration Phase Objectives:
    - Run Application Accelerator

    - DCO Sessions

    - Work Iteratively

    - Engage the PMF (Create Data)

    • - Engage TMF
    • >Create Test Plan
    • >Develop Test Scenario

    46
  47. Construction Phase Objectives
    • - DCO Session details, assign work to configure the product ready application in iterations
    • >PMF can be used to structure

    • - Complete Config. and Unit Test
    • >TMF can be used

    - Run Application test scripts and begin system test

    - Build and test migration plans

    47

What would you like to do?

Home > Flashcards > Print Preview