Further Review Flashcards
Slide 27
Accuracy vs Precision: need to understand better and how it ties into control charts, processes, improving adjusting equipment or deliverable process. Need multiple question examples
Find few sample questions on quizzes and exam?
Example of Deliverable Process being Measured
* Process Steps: Reqs gathering, design, development, testing, deployment, feedback.
* Measuring Outcomes:
* Target Value: Features should reduce user task completion time by 20%
* Data Collection: After deploying features, collect data on task completion times from a sample of users.
* Compare the new task completion times to the old ones.
* Results:
* Far from Target Value: Feature only reduces task completion time by 5%(Low Accuracy)
* Consistent Results: Every user shows a 5% reduction(high prec)
Improving Process
* Review Reqs:Reasses initial reqs to ensure captured correctly on what is need to get 20% reduction.
* Design Adjustment: Modify the design to better meet the requirements.
* Iterative Development: Implement changes in small increments, continuously testing and refining.
* User Testing: Conduct more thorough user testing to ID where process diverges from target.
* Feedback loops: To align outcomes w/ desired results.
Summary process(prec v acc): Improving deliverable process involves revisiting each step to ensure that it’s accurate and effectively meets the target outcome. Doing so addresses the root cause of the issue, ensuring process accurate and consistent.
Equipment questions will give you actual examples of measurements: 10lb, 12lbs ..
Slide 30 col 1
What are the different types of surveys give to customer or the team called, know the different.
NPS: Measures customers willingness to recommend product/service to others. Gauges customers overall satisfaction w/ orgs prod/serv and customer loyalty
Memorize NPS means Net Promoter score, didn’t know what acronym meant on exam.
EX2.Q.100
You’re an Agile PM. With No PO on team. A High level SH(exec) wants new feature added. What next?
a. Place Feature in the and PBL Prioritize it w/ C/B.
b. Gather Requirements for new feature and have team elaborate on it.
Place feature in PBL and prioritize it w/ C/B or Gather Requirements for new feature and have team elaborate on it?
Steps to handle feature request
Document Request in PBL: Add feature request to PBL:
No reqs yet, just a simple PBL item US, still has US format but not fully detailed(w/ reqs or AC). Just a place holder story.
Initial Prioritization: Do high level cost-benefit analysis to assess the value and cost of feature. Helps understand where it fits in priority.
Gather Detailed Requirements: Collab w/ SHs to gather detailed reqs for feature. Can involve creating USs and Acc.Crit
BL Refinement(Team involvement): Scrum team elaborate on requirements, discuss feasibility & technical implications. Estimate effort(sps)
Re-Prioritization: Re-Evaluate the priority of the new feature against existing items in PBL, using insights from team and initial C/B analysis. Team can use Moscow, or other prtzn techs.
Sprint Planning: Discuss Prtzd PBL items, including new feature(if high enough in prty). Team selects item from backlog(including new feature if it fits w/in sprint goal and capacity)
Come back and Review not sure.
Major change needed to the Scope Baseline shoud we review Change MP or Scope MP?
a. CMP(change process & CCB)
b. SMP(see how changes to scope handled)?
Scope MP: Might have guidelines on how to handle changes to scope, but main purpose is for defining and controlling what should be and not be included in scope.
* Outlines(high level, not detailed) processes for scope changes but does not detail WORKFLOW and IMPACT analysis as thoroughly as Change MP
Change MP: Outline Change Process for handling changes to the project, including how to document, evaluate, and approve changes.
* Approval process: Includes details on Roles/Reps of CCB and specific steps for submitting and approving CR’s.
* Impact Analysis: This plan usually involves steps for conducting an impact analysis to understand the implications of the change on scope, budget, sched, and resources.
Revise
Who created Plan Do Check?
William Edwards
Revise more detail
Who made the analyzing and improving processes for Continuous Improvement?
* To improve the performance of everyone,
Deming
Revise more detail
Who emphasized the importance of continuous Improvement
Juran emphasized the importance of continuous improvement,
Revise
Who pioneered the need for organizations to meet customer expectations
Crosby
What’s the difference between Relationships and Dependencies
Revise FC Slide 34
Need to know scheduling sequence for Define actv, seq actv, estimate actv durations, dev sched and Resource Mgmt: Plan resc mgmt. and estimate actv dur
- Plan Project Schedule Process: Process to develop and control project Schedule
- Define Activities: Decompose Work packages to make activity list
- Sequence Activities: See what are predecessor/successor orders and creating a schedule network diagram.
* 4 types of relationsips: FS, SS, SF, FF
* 4 types of Dependencies: Mand, discrectionary, internal, external
* Leads and lags
What are Feature Driven Developments Roles?
- Project Manager: Oversees the entire project(progress, budget, scope).
- Chief Architect: Oversees, plans and manages the overall design of system architecture.
- Development Manager: Leads the feature design and implementation, mentors/leads development team daily.
- Chief Programmer: Designs and analyzes features, often managing small teams.
- Class Owners: Responsible for designing, coding, testing, and documenting features. Works closely w/ chief programmer to implement features..
- Domain Expert: Provides business knowledge and makes sure requirements are met, w/ insights into customer needs.
Role interdependencies
* Chief Architects design desigion influence the chief programmers work, while chief programmer provides feedback on design feasibility and implementation.
* Chief Programmer: oversees dev process and guides Class owners.
* Class owners rely on Domain experts for accurate requirements and domain knowledge to ensure feature relevance and correctness.
* Domain experts input helps the chief architect make informed decisions based on biz needs.
Heavy reliance on Chief Programmer
What are Feature Driven Developments Engineering Best Practices?
- Feature Teams: Teams dedicated to specific features.
- Individual Class Ownership: Each class (group of code) is owned by a single person.
- Domain Object Modeling: Use models like sequence or context diagrams to represent the system.
- Inspections: Regular code and design inspections(Pair programming.
- Configuration Management: Manage versions of changes systematically.
- Regular Builds: Continuously integrate code into a test system.
- Visibility of Progress: Track progress through visible metrics like Kanban boards.
What is Feature Driven Development? FDD
It’s steps?
An Agile methodology focusing on delivering working software by developing features—small pieces of usable functionality that bring business value. It’s particularly suited for** large, complex projects **with clear requirements.
* Features: Small functional units that provide value to the user.
* The focus is on planning, designgin and building these features sequentially.
FDD Iterative Process: FDD** consists of five main activities** performed iteratively
1. Develop High-Level Model: Create an overview of the system.
2. Develop Features List: Define all features from the model.
3. Plan by Feature: Prioritize features and plan their development.
4. Design by Feature: Focus on designing individual features.
5. Build by Feature: Code and test the feature, then integrate it.
FDD is scalable and suitable for both small and large teams(Feature teams).
