Managing project with the Fsoft Insight
•Download as PPT, PDF•
1 like•1,389 views
Practical use of Fsoft Insight for managing projects Targeted attendees: Team leaders, PQA, SQA, project managers Case study: Create new project Create WO Define project parameters Create products Plan effort and schedule Record requirements Plan defect Identify risk
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Managing project with the Fsoft Insight
Similar to Managing project with the Fsoft Insight (20)
More from Mobi Marketing
More from Mobi Marketing (20)
Recently uploaded
Recently uploaded (20)
Managing project with the Fsoft Insight
- 1. Managing project with the Fsoft Insight Version: 1.1 Author: Le The Hung 10-Nov-2003 Instructor: Le The Hung Head of SEPG © 2003 FPT-SOFT 04e-BM/NS/HDCV/FSOFT
- 2. Introduction Course duration: 2 hours Purpose: Practical use of Fsoft Insight for managing projects Targeted attendees: Team leaders, PQA, SQA, project managers Tests/quiz: Case study in 30’ for new attendants
- 5. Fsoft Insight: 3 in 1 Project Data (Mgmt: T/S, DMS,...) (Dev: est., sche., req...) Project Info (Project DB) Project Postmor tem Data Software Process DB and Assets Norms Software PCB Supporting PCBs OSDC/FSOFT Final Info OSDC/FSOFT WIP Info Quality Data (Control, audit) Supporting Data (HRM, Training, Fin., Adm., Network) Extranet DSS Viewer DSS INPUT APPROVE WIP AREA FINAL AREA PROJECT AREA OSDC/FSOFT AREA DSS DSS Timesheet DMS Other tools Tools (Excel) Tools (Excel) INPUT INPUT APPROVE Project Info (Postmortem) APPROVE Processed (secondary) data Raw (primary) data Read access Input data Tool Data presentation Legend FSOFT Mgmt Suite - System view APPROVE Dissemination Dissemination Dissemination Dissemination Prj member SQA/PQA Staff Supporting Staff Supporting Process DB and Assets APPROVE PORTAL (My FMS) APPROVE For grouping purpose only
- 33. Thank you Questions and Answers
Editor's Notes
- 02/24/11 There are 3 purposes of the Fsoft Insight: Project planning and monitoring Organization planning and monitoring Quantitative process management Notes: All features have to be completed this year. This R2 covers all requirements related to project planning and monitoring Reference: FMS vision document
- Process and RADIO: Group Leader informs SEPG the planned start date, planned end date and resource allocation of the project SEPG creates new project in Dashboard/Fsoft Insight based on GL information SEPG assigns rights for PMs to manage project in Fsoft Insight Notes: Resource allocation is done in the Dashboard The project status is updated in the Dashboard. It’s “Tentative” until the kick of meeting is conducted and the WO is approved Reference: Guidelines: Project planning and management
- Process and RADIO: PM accesses to Fsoft Insight using Tool account and password PM selects WO feature and fill up required information of all pages, except Deliverable page. PM selects Product feature to create list of products that will be delivered to customers, then PM goes back to WO feature and fills up the Deliverable page (see next 2 slides) PM inform reviewers and approvers about the completion of the WO Reviewers and approvers review the WO and send comments to PM, or click on Approve if there is no comment. Notes: SEPG will assign right for some project members to view or manage some project information by PM’ request Reference: Guidelines: Project planning and management Templates: WO/AN, Project databases
- Process: Select product feature Create products with required information. Notes: The list of work products is managed by SEPG that is the same for Timesheet, DMS and Fsoft Insight. The size of project/stage is calculated in the UCP converted from all size estimation methodologies. Use the reuse ratio for products that are reused from previous versions The size of a stage is summarized by the size of all product of the stage. A product is belong a stage if it’ release date is in the duration of the stage. So that project has to fill the planned release date of all products defined (see Schedule feature, Review and test activity section). Reference: Guidelines: Project planning and management Guidelines: Software estimation Templates: Project database
- Process: Select WO/Deliverable Add new deliverable selecting from product list Add committed date for the deliverable Do 2&3 for all deliverables Notes: The status of a deliverable which is in progress of production is “In progress” Reference: Guidelines: Project planning and management Template: WO/AN, Project database
- Process: Go to Requirement feature Add new requirement with required information. Go to Parameter feature, select Distr. rates and update the Completeness rate tailored in the project for tracking the requirement completion. Notes: Each requirement has to be assigned to a deliverable. Reference: Guidelines: Requirement management Templates: Project database
- Process: Go to Project plan feature Select Lifecycle section Create stages and fill up required fields Create iterations and fill up required fields Create a tailoring/deviation Notes: If project start date is not be planned there will be a error creating a stage First stage has to be Initiation with the start date is the project start date. Last stage has to be Termination with the end date is the project end date Use the process tailoring guidelines (Excel file) for selecting suitable tailoring. Reference: Standard: Standard lifecycle models Guidelines: Process tailoring Templates: Project database
- Process: Go to Project plan feature Select Dev. & Dep. section, go to Critical Dependencies table Add a critical dependency and fill up required fields Select other sections and define schedule for each required activity Notes: The schedule for quality gate conduction is mandatory for each stage The internal audit scheduling is mandatory for all projects Reference: Guidelines: Project planning and management Templates: Project database
- Process: Go to Effort feature Select a section Select an item and fill up estimated effort comparing with the norm effort and using WBS estimation. Do 2&3 for each section. In order to plan effort for review and test, project has to plan defects to be found first (see next slide) Notes: Norm of stage effort for each standard stage = Project planned effort x Effort distribution rate for the stage Norm of process effort for each process = Project planned effort x Effort distribution rate for the process Norm of Review effort = Weighted defect planned in review/Norm of Review effectiveness Norm of Test effort = Weighted defect planned in test/Norm of Test effectiveness Reference: Guidelines: Project planning and management Templates: Project database
- Process: Go to Defect feature Select an table and fill up planned defect found fields Select detail defect plan to plan defect found for each product (and/or work product) Notes: Norm of review defects of each process = (Size of project x Norm of defect rate – Planned leakage) x Norm of defect removal efficiency in review x Defect distribution rate for the process. Norm of test defects of each process = (Size of project x Norm of defect rate – Planned leakage) x Norm of defect removal efficiency in test x Defect distribution rate for the process. Fill up planned defect found for a module based on planned software quality control activities (test, review) to be done in project progress Reference: Guidelines: Project planning and management Templates: Project database
- Process: Go to Project plan feature Select Overview section and go to Risk table Select Add new risk Fill up required fields Notes: Contract review is a mandatory source of risks. Use the Software process asset for studying risks occurred in Fsoft project. Reference: Guidelines: Risk management Templates: Project database
- Process: Go to CI Register feature Click on Update Fill up Baseline for each product Notes: Each CI with it’ version is a product Reference: Guidelines: Configuration management Templates: Project database
- Process: Go to Requirement feature Select a Requirement that has to be updated Fill up required fields Notes: You can use Batch edit for editing a set of requirements Reference: Guidelines: Requirement management Templates: Project database
- Process: Go to Schedule feature Select an section and an item Fill up required fields Notes: Project can do the re-planning only at milestone for next stages Reference: Guidelines: Project planning and management Templates: Project database
- Process: Go to Effort feature Select an section and an item for re-planning Fill up required fields Notes: Actual effort has to be filled for quality activity manually Project can do the re-planning only at milestone for next stages Reference: Guidelines: Project planning and management Templates: Project database
- Process: Go to Defect feature Select an item for re-planning Fill up re-plan defect field Notes: Project can do the re-planning only at milestone for next stages Reference: Guidelines: Project planning and management Templates: Project database
- Process: Go to Risk feature Select a planned risk or select Add new risk Fill up required fields Fill the issues caused by the risk in the Issue feature for managing Notes: The risk assessment is conducted at milestones as mandatory Click “Unplanned” for adding New occurred risk Reference: Guidelines: Risk management Templates: Project database
- Process: Go to Issue feature Select add New issue or update Current issues Fill up required fields Notes: The solution has to be defined for each issue Reference: Guidelines: Project planning and management Templates: Project database
- Process: Go to CI Register feature Click on Update button Select a product and tick on the promotion stage of the product Notes: Reference: Guidelines: Configuration management Templates: Project database
- Process: Go to Weekly report feature View all sections and find issues based on Effort status Go to Issue feature to record issue if any. Return to Weekly report feature Write comments Click on the Submit weekly report button to update weekly data in Dashboard. Notes: Effort status = Spent effort/Budget effort/Requirement completion Reference: Guidelines: Project planning and management Templates: Project database
- Process: Go to Milestone report feature View all sections Find issues based on Red color of Effort, Schedule and Defect statuses and Quality objective deviations Go to Issue feature to record issue if any. Return to Milestone report feature Write comments Notes: Schedule status = Stage deviation/Norm of stage deviation Defect status = Weighted defect planned/Weighted defect found Defect status is analyzed only in case when a review (or test) planned activity had been completed Reference: Guidelines: Project planning and management Template: Project database
- Process: Go to WO feature Select an item to be changed and do the change Go to Change section of WO to add comments for the changes Inform RADIO related persons for review/approve these changes Notes: In the case when a deviation is less than 30%, the project can re-plan related item in the PP but not in the WO Reference: Guidelines: Project planning and management Templates: WO/AN
- Process: Go to Post mortem report feature View all sections Go to Cause analysis section, select an item, study it and do the causal analysis If needed fill in the future work section Notes: Use related features/tables for finding information to analyze deviations. Reference: Guidelines: Project planning and management Templates: Project database
- Process: Go to Post mortem report feature View all sections Go to Cause analysis section, select an item, study it and do the causal analysis If needed fill in the future work section Notes: Use related features/tables for finding information to analyze deviations. Reference: Guidelines: Project planning and management Templates: Project database
- Process and RADIO: PM goes to WO feature, selects Acceptance section and fills up fields PM informs RADIO related persons to review/approve Reviewers and approvers review all sections, inform PM if any or select the Signature page for approving SEPG verifies project data and decides to close the project Notes: Reference: Guidelines: Project planning and management Template: WO/AN
- Process: Training conductor selects an attendant for doing each exercise All attendants review and comments Notes: Don’t spend more 5’ for each exercise