Development Approach & Life Cycles Flashcards

1
Q

What are the Life Cycle Phases used in all development cycles?

A

1.Feasibility — Determines if the business case is valid and if the organization has the capability to deliver the intended outcome.
* Evaluates the project idea and its practicality.
* Usually done w/ business case or a PO is coming up with feature ideas.

2.Design — Planning and analysis lead to the design(Project plan/Blueprints) of a project’s deliverable(s).
* Defines requirements and develops specifications. Blueprints
* Equivalent to Planning phase: creating PM plan.

3.Build — Construction of the deliverable(s) with integrated quality assurance activities.
* The solution is developed based on design
* This is when we build the feature w/ our dev team or people doing the work.

4.Test — This is where we test what we have created, make sure that it meets our customer requirements.
* Final quality review and inspection are carried out before Deploy Phase(transition, go-live, or acceptance by the customer.)
* The product is tested, including validation(validate meets reqs qlty metrics) testing in production
* Test can overlap with development(website project) to make sure site works as planned.

5.Deploy — Project deliverables are put into use in live environment and transitional activities required for sustainment, benefits realization, and org change management are completed
* If deployed it’s multiple releases, this may overlap with development and testing
* The validated release is deployed to users after stakeholder approval
* Deploy Phase Includes: Actual release of the product, often involves staging, installation, and activation of solution.
* Validation: Ensuring deployment successful, including production testing to verify functionality.
* User Training and Handoff: Ops team and end users receive training and documentation.
* This is also considered the transition phase, where we also validate the release .

Dev Life Cycle use for life cyce phases:
* Predictive: Performs all phases once.
* Adaptive: Performs once per increment( each sprint like mini project does all steps.
* Kanban: Flow based no phase. It is a pull approach.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

In a Life Cycle Approach what is the feasibility step for?

A

This phase is to assess whether the project is viable and worth pursuing. It invovles identifying potential risks, benefits, costs, and technical challanges.

Connected to PM Life cycle: Initiation phase. Feasibility study creates project charter and other initation docs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Whats the difference between a project development life cycle and a predictive project management life cycle?

A

Project Development LC: or product life cycle that focuses on the phases of developing and delivering a product or solution. It’s typically associated with predictive (waterfall) methodologies but can apply to other approaches as well.
* Feasibility>Design>Build>Test>Deploy> Close
* Product/solution development focused
* Predictive

Project Management Predictive Life Cycle(PMI): This sequence represents the project management life cycle as defined by PMI (Project Management Institute) and is typically used in the predictive project management methodology.
* Initiation: Defining the project at a high level, including objectives, scope, and stakeholders, and obtaining authorization to start the project.
* Plan: Developing a detailed project management plan that outlines how the project will be executed, monitored, and controlled.
* Execute: Performing the work defined in the project management plan to achieve the project’s objectives.
* Monitor and Control: Tracking, reviewing, and regulating the project’s performance and progress to ensure alignment with the plan, and making adjustments as necessary.
* Close: Finalizing all project activities across all phases to formally close the project.
*

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is the Design Phase of a project life cycle step?

A

Design Phase: Planning and analysis lead to the deisgn of the project deliverables that will be developed(PM Plan)
* involves creating detailed specifications, blueprints, and models for the product or system.

Connection: To Planning phase of PM Process Group.
* Design phase provides the technical requirements and specifications that are incorporated into the **project management plan. **
* The planning phase ensures that all aspects of the design are accounted for in terms of resources, timelines, and risks.
* Design Stage>Technical Reqs(blueprints)>Put into PMPlan.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the Build Phase of a project life cycle step?

A

Build: Construction of the deliverable with** integrated quaity assurance activities** is conducted.
* In the product life cycle, the build phase involves the actual development or construction of the product based on the design specifications.

Connection: The build phase represents the technical execution of the project. The project management execution phase ensures that the building activities are aligned with the plan, resources are allocated correctly, and the work is performed efficiently.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is the Test Phase of a Project life cycle?

A

Test: Final quality review and inspection of deliverables are carried out before transition, go-live, or acceptance of customer
* In the product life cycle, the testing phase involves verifying that the product meets the specified requirements and functions correctly.

Connection(M&C): The testing phase is where the product is evaluated against the criteria set out in the planning phase. **Monitoring and controlling **ensure that any issues identified during testing are addressed, changes are managed, and the project stays on track in terms of time, cost, and quality.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is the Close Phase of a Project life cycle?

A

Close: The project is closed, project knowledge and artifacts are archived, project team members are released, and contracts closed.
* Both the product life cycle and the project management life cycle culminate in the closing phase. This involves finalizing all project activities, handing over deliverables, closing contracts, and conducting lessons learned reviews.

Connection: The closing phase ensures that the project is formally completed, the product is delivered and accepted, and all project documentation is finalized. It marks the end of both the product development process and the project management process.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is the Deploy Phase of a Project life cycle?

A

Deploy: Project deliverables are put into live environment and transitional activities required for sustainment, benefits realization, and** org change management** are completed.
* In the product life cycle, deployment involves rolling out the product to the end-users or customers, ensuring it is fully operational and meets their needs. Includes
* Validation: Ensuring deployment successful(install included), including production testing to verify functionality.
* Includes Production deployment testing, active SH particpation is deliverable working as needed, SH satisfaction survey( they happy with the result)
* User Training and Handoff: Ops team and end users receive training and documentation.
* This is also considered the transition phase, where we also validate the release .

Connection: Mostly done in Closing phase

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is a multiple delivery cadence for project life cycle.

A

The project is broken into phases, with distinct deliverables at various stages, each representing a completion of a specific segment of the project.
* Each phase has seperate control, testing, and acceptance before moving forward.
* Ex: Project to develop a new drug may have multiple deliveries, such as preclinical trials. PH1- trial result, PH2- trial results, PH3 trial results, Regulatory approvals, and then launch.
* Ex: Building Project: Deliverables- foundation, structural framework, interior finishes, each with approvals.

Difference between single delivery
* Entire building is handed over at once, usually at end of project. All phases interconnected with no intermediate delivery until project is fully finished.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Whats the difference between Single Delivery and Multiple delivery projects?

A

Single delivery projects are ideal for straightforward, end-to-end projects where all elements must come together as one cohesive whole, while multiple delivery projects suit more complex or segmented builds where independent phases can be completed and utilized separately.

  • Single Delivery: The entire project is planned, executed, and completed as one continuous flow, with a single final output at the end.
  • Mult Deliveries: The project is broken into phases, with distinct deliverables at various stages, each representing a completion of a specific segment of the project.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What are the steps for development cycle of Incremental life cycle?

A

Def: The incremental project life cycle is an iterative approach to project management. It divides the project into smaller increments or cycles and delivers a working product at the end of each cycle. Each increment builds upon the previous one, incorporating feedback and making improvements. This life cycle allows for flexibility and adaptability to changes.

  • Concept(Feasibility): In this phase, the project concept is defined, including the high-level objectives and scope. This phase helps in determining if the project is feasible and aligns with the organization’s goals.
  • Planning and Requirements: The planning and requirements phase focuses on :
    * Gathering detailed requirements and developing a project plan for the** first increment. **
    • It involves creating a prioritized list(PBL) of features, estimating effort, and defining the schedule and resources needed.
  • Design and Development: The design and development phase involves creating a detailed design for the **first increment **and then implementing it.
    • It includes coding, testing, and integrating the developed components.
  • Testing and Evaluation: The testing and evaluation phase verifies that the **first increment meets **the **specified requirements. **
    • Defects are** identified and resolved,** and** user feedback is gathered** to** incorporate improvements and address any issues.**
  • Deployment and Feedback: This phase focuses on deploying the first increment(MVP) to the users and **gathering feedback. **
    • The user’s experience and feedback help refine the product and prioritize requirements for subsequent increments.

Characteristics:
* The incremental project life cycle offers increased flexibility and adaptability. **
* It allows for e
arly delivery of working functionality** and** incorporates user feedback** throughout the project.
* The iterative nature of the cycle enables adjustments to be made based on changing requirements.
* However, it requires effective communication and collaboration with stakeholders, as their involvement is crucial at each phase.
* It is suitable for projects with evolving requirements and uncertain environments.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are the steps for development cycle of Iterative life cycle?

A

Definition: The iterative project life cycle is a cyclical approach to project management. It involves repeating a set of phases in multiple iterations or cycles until the project goals are met.
Each iteration builds upon the previous one, incorporating lessons learned and making improvements.
This life cycle allows for continuous refinement and provides opportunities for regular feedback and validation.

Phases

  • Initiation and Planning: In the initiation and planning phase,
    • The project’s objectives and scope are defined, and a
    • High-level plan is developed.
    • It also involves identifying risks and constraints and allocating initial resources.
  • Design and Development: The design and development phase focuses on creating a detailed design for the project’s deliverables and then implementing them.
    • This phase activities like: coding, testing, and integrating the components.
  • Evaluation and Feedback: The evaluation and feedback phase involves evaluating the project’s deliverables against the defined requirements and obtaining feedback from stakeholders.
    • This feedback helps refine the design and prioritize changes for the next iteration.
  • Refinement and Improvement: The refinement and improvement phase incorporates the feedback received and makes necessary adjustments to the project’s design, development, and planning.
    • It includes addressing any identified issues, resolving defects, and adapting to changes.
  • Repeat: The above phases are repeated in multiple iterations until the project goals are achieved.
    • Each iteration builds upon the previous one, incorporating feedback and making improvements.
    • This iterative process allows for regular validation, adjustment, and improvement of the project.

Characteristics

The iterative project life cycle promotes continuous refinement and improvement. It encourages early validation and feedback, allowing for the incorporation of changes and minimizing rework.
The cyclic nature of the cycle enables regular checkpoints and course correction as needed.
However, it requires effective project tracking and management to ensure that the iterations stay on track and align with the project goals.
It is suitable for projects with evolving requirements and a need for regular validation and adjustment.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are the steps for development cycle of Agile life cycle?

A

Definition: The Agile project life cycle, also known as the agile life cycle, is an iterative and incremental approach to project management.
* It emphasizes adaptability, collaboration, and continuous improvement.
* This life cycle is specifically designed for projects with rapidly changing requirements and a need for maximum flexibility.

Phases

  • Plan: The plan phase focuses on identifying the project’s objectives and scope and developing initial plans.
    • It involves creating a prioritized list of features, estimating efforts, and defining a high-level project roadmap.
  • Design: In the design phase, detailed designs are created for the project’s deliverables.
    • This includes creating user stories, wireframes, and prototypes.
    • Collaboration and feedback gathering from stakeholders play a vital role in this phase.
  • Develop: The development phase involves coding, testing, and integrating the product’s components as per the defined designs.
    • It includes frequent iterations and releases of working functionality.
  • Test: The testing phase focuses on ensuring the quality and functionality of the product.
    • It involves conducting various types of testing, including unit testing, integration testing, and user acceptance testing.
    • Defects are identified and resolved promptly.
  • Deploy: The deploy phase involves releasing the developed functionality to the users, usually in small increments.
    • It includes feedback gathering and user acceptance validation.
  • Review and Adapt: The review and adapt phase involves continuous review and improvement of the project processes and deliverables.
  • It includes retrospective meetings to capture lessons learned, identify areas for improvement, and make necessary adjustments.

Characteristics

  • The extreme project life cycle offers maximum flexibility, adaptability, and collaboration.
  • It allows for rapid response to changing requirements and e**ncourages continuous delivery of working functionality. **
  • The iterative and incremental nature of the cycle supports regular feedback and validation.
  • Effective communication and collaboration among stakeholders, as well as self-organizing project teams, are essential for success.
    It is suitable for projects with highly dynamic and rapidly changing requirements.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Agile Framework: Disciplined Agile what is it and it’s phased?

A

Hybrid approach Tool Kit
It’s more of an agile tool kit where you can pull from any fw Kanban, scrum, SAFe, to tailor to your project or org to suit your needs.

DA Phases:
Inception
Construction
Transition

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Insert DIAGRAM

What are the steps/sequence to each of the Development Approaches?

A

Development Approach Steps: All Dev approaches have same steps, but used differently

Predictive: Analyze(reqs)>Design>Build>Test>Deliver
Iterative:Analyze>Analyze/Design(Feedback->prototype)>Build/Test(Feedback->Refine build)>Deliver

Analyze/Design: Get feedback and build small prototypes to make sure that’s what SH wants.

Build/Test: Proto done. Build product, get feedback and refine until correct.

Incremental: Do all project steps for each increment, like each is a small project.
Increment 1: Analyze(reqs)>Design>Build>Test>Deliver(Inc 1)
Increment 2: Analyze(reqs)>Design>Build>Test>Deliver(Inc 2)
Increment 3: Analyze(reqs)>Design>Build>Test>Deliver(Inc 3)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

XP Practices

A

Root cause analysis, pay per use(Feature w/ most revenue value)
* Feature Teams: Team experts on that feature work on it

17
Q

FDD vs Scrum

A

FDD: Focus on delivering features
* Model driven approach W/ up front planning
* Used on large complex projects w/ clear requirements that can be broken in FEATURE LIST
* Roles: Chief Architect, Chief Programmer, Domain Expert, Object Owner
SCRUM: Focus on delivering US
* Flexile, team collab, adaptive planning
* Deliver small units of work in timebox
* Reqs> PBL

18
Q

Crystal Methods Dev method

A

Designed to scale and realizes each project may need slight tailoring based on complexity and Size(# people)People cententric: Focus on people, communications, and team specific tailoring
* Different variants clear, yellow, orange for diff context.
* A family of methodologies designed to scale based on project size(#people in project) and criticality of project.
* Use Case: Suitable for teams that need high flexibilibty and people centric approach, where processes and practices are adapated to team context.

19
Q

Dyanamic Systems Developmen Method: Constraints Triangel comes from= Scope variable, sched locked, cost locked.

A