Agile Project Management Flashcards

1
Q

Differences between process and project management

A

Process:
Repeat process or product
Several objectives
Ongoing
People are homogenous
Well-established systems
Greater certainty
Part of line organization
Established practices
Supports status quo

Project:
New process or product
One objective
One-shot-limited life
More heterogeneous
Integrated system efforts
Greater uncertainty
Outside of line organization
Violates established practice
Upsets status quo

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

What is the difference of Project Work and day-to-day activities/ tasks?
Projects vs Ongoing tasks

A

Projects: one-time, have a specific goal, limited by certain pre-defined parameters
Ongoing tasks and operations: Things that need to be done on a permanent basis to keep the product/service provision of the organization going

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

What is a Project?

A

• Projects are complex, one-time processes
• Projects are limited by budget, schedule, and resources
• Projects are developed to resolve a clear goal or set of goals
• Projects are customer-focused

A project is a temporary task created to produce something new, like a product, service, or result.

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

What is Project Management?

A

Project management helps to guide the project work to deliver the intended outcomes. It’s the application of knowledge, skills, and tools, to activities to meet project requirements.

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

Project life cycle

A

A project life cycle refers to the stages in a project’s development and are divided into 4 distinct phases:

  • Conceptualization: development of the initial goal and technical specifications of the project. Key stakeholders are identified and signed on at this phase.
  • Planning: all detailed specifications, schedules, schematics, and plans are developed.
  • Execution: the actual “work” of the project is performed
  • Termination: project is transferred to the customer, resources reassigned, project is closed out.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Project Components

A

Client Interest: level of enthusiasm or concern, of the customer. Clients could be from within your team or external customers.
Project Stake: it’s the level of investment the organization has in the project. The longer the life of the project, the greater the investment. If a lot of time, money, or effort is put into it, the project becomes more critical.
Resources: Commitment of financial, human, and technical resources needed to make the project happen.
Creativity: level or amount of innovation required by the project, especially during certain development phases. Some projects need a lot of creative solutions, especially when they involve new or unique ideas.
Uncertainty:This is about the level of risks the project might face. Riskiness is the number of unknowns, and challenges the project might face. At the start, there’s usually more uncertainty because many problems haven’t been identified yet, nor addressed.

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

How projects success is measured?
(Factors)

A

Budget
Client Acceptance
Time
Performance

Costs
Achievement of defined milestones (see next slide)
- How “happy” the customer is (internal/external):
- Measured based on the fulfillment of the project specifications and/or customer needs
On time vs. delayed
Execution quality (disturbances, blocking times, resource occupation
Commercial success achieved (the part that is measurable today)
The eventual success of a project is only determined at a later time, not immediately upon project delivery (in many cases

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

What are Project Milestones?

A

Milestones are events or stages of the project that represent a significant accomplishment

Benefits of defining project milestones:
1. Signal completion of important steps
2. Motivate team and suppliers
3. Offer reevaluation points
4. Help coordinate schedules
5. Signal other team members when their participation begins

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

Why projects terminate? Reasons for project termination

A

Extinction
Addition
Integration
Starvation

Extinction : This occurs when the project ends because it has achieved its objectives or failed completely.
Addition: The project becomes a permanent part of the organization.
Integration: The project’s outputs, team, or resources are absorbed into other parts of the organization.
Starvation: This happens when a project is deliberately or unintentionally deprived of resources (e.g., funding, staff, or time). As a result, the project is forced to stop without officially being declared terminated

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

What’s Agile Project management?

A

Agile Project Management (Agile PM) is a new era in project planning that focuses on flexibility and changing customer requirements.

• Planning the work and then working the plan
• Customer needs may evolve and change over course of project
• Importance of evolving customer needs leads to incremental, iterative planning process

  • Agile is a form of adaptive or change-driven project management that largely reacts to what has happened in the early or previous stages of a project rather than planning everything in detail from the start.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Difference between agile project management and classical management (waterfall model)

A

Waterfall project development process works well when:
• Requirements are very well understood and fixed at the outset of the project
• Product definition is stable and not subject to changes
• Technology is understood
• Ample resources with required expertise are available freely
• The project is (typically) of short duration

Agile:
Flexible, adaptive and iterative.
Adapts to feedback and changing customer needs to ensure customer satisfaction.
• Encourages collaborative teams.

Waterfall:
Rigid and sequential.
Changes are difficult and expensive once the project has started.
Interaction with customer limited to the initial requirements
Fixed plan with no room for adaptation
Little to no Feedback during the project
Collaboration is limited

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

Understanding of how does scrum work in project management

A

• Agile PM, by using Scrum, Agile Project Management, especially with Scrum, avoids the mistake of thinking a project will go exactly as planned from the start.

• Flexible, iterative system designed for the challenge of managing projects in midst of change and uncertainty
• “Rolling wave” process of continuous plan-execute-evaluate cycle
• Emphasis on adaptation, flexibility, and coordinated efforts of multiple disciplines

It helps to adapt changing customer needs or market trends, and adjusts to them. It uses a “Rolling wave” process of a continuous plan - execute - evaluate cycle. Scrum breaks work into short steps called sprints, where teams deliver these tasks and get feedback to improve. Scrum is a flexible and iterative system designed to handle uncertainty and change.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q
  1. Terms in agile project management:
A

Generalized specialists: Very good at one thing, but also competent at a wide variety of work.
Improve collaboration: When one worker has problems. others help and learn together
Courage: Tell the truth, work together, adaptto changes, question status quo, have difficult conversations
Collective ownership: All qualified team members are responsible for product, and all can change it.
Openness : Seek new ideas. ask for help when needed
Pair programming: Practice of one programmer writing while another reviews, two minds are better than one.
Developmental leadership: Safe environment in which different team members informally take on leadership roles at different times and are supported by team members and other stakeholders.
Servant leadership: Leader focuses on needs of the followers first through integrating followers’ needs with project goals, honesty, delegation, and empowerment.
Transformational leadership: Leader aims to develop trust and alian personal values of individuals (followers) to accomplish vision and mission of the
oreanizauon
Respect: Everyone gives and feels respect, everyone contributes, team strength is collaboration, give each other permission.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q
  1. Terms in Agile Project Management
A

Customer prioritization:Decide importance or urgency of work based on customer input
Customer driven value: Define value from a customer’s perspective
Minimum viable product (MVP): The simplest version of a product with just enough features to gain quick customer feedback
Prioritized backlog: Desired products prioritized by business value and risk
Product: The deliverables that are created in an Agile project
Product backlog: A wish-list of things that may be created by the project team
Product Roadmap: Visual showing high-level plans of products expected to be created during each release
Refine requirements: Use feedback to progressively understand true needs
Release: Period when functionality is created and transitioned to users
Risk-adjusted backlog: To-do prioritized list of work to both create product and reduce risk
Solutions: Deliverables that are usable, desirable, and functional in helping customers achieve desired outcomes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q
  1. Terms in Agile Project Management
A

Continuously Identify Risks: Specific effort to use feedback and engage team to identify risks.
Premortum: Brainstorming description of what could go wrong
Assume Variability: Preserve options to provide flexibility because of unknowns.
Handoffs: Whenever work is turned over some tacit knowledge is lost.
Risk-based Spike: Short time-boxed work to address a specific risk.

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

What is Digital Workplace? What does digital workspace entail?

A

Digital workplace is the first step to take work beyond the borders of the physical office
• This enables access to a bigger pool of talents
• Also enabling people to work securely anywhere, anytime and on any device
• It is not only about the technology applied to and at work
it sees anthe a perse cut teer, the policies that the company sets for its species everything agiologies to play a major role in modern project management.
• Workplaces become complicated because of the pluralistic needs of the workforce

A digital workspace is a virtual environment that enables individuals
and teams to perform work-related tasks, collaborate, and access tools, data, and applications from anywhere, using internet-enabled devices. It is designed to provide a centralized, seamless experience, that integrates various digital tools and resources to enhance productivity, communication, and flexibility.

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

Stakeholder management

A

Every business has stakeholders
Every project has stakeholders

Stakeholder analysis is a useful tool for revealing conflicts that may appear unavoidable during the planning and implementation of new projects.
Project stakeholders are defined as all individuals or groups who have an active stake in the project and can potentially impact, either positively or negatively, its development.

Stakeholder management involves identifying, understanding, and engaging with people who can influence a project.

Identification: Recognizing all potential stakeholders, including those who might be internal (team members, executives) or external (customers, regulatory bodies).
Analysis: Assessing their level of influence, interest, and potential impact on the project.
Developing strategies to communicate regularly and appropriately, keeping stakeholders informed and involved. This can include meetings, reports, or informal updates.

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

What are the common project stakeholders?

A

Project Manager
Top Management
Other Functional Managers
Clients
Parent Organization
External Environment
Accountant
Project Team

19
Q

What is organizational culture?

A
  • Unwritten
  • Rules of behavior
  • Held by some subset of the organization (or all organizational members)
  • Taught to all new members
  • Can be a formally desired (planned) culture or an ad hoc established culture
  • Leaders go by example showing and giving the culture further into the organization
    Organizational culture is unwritten, refers to the shared values, beliefs and behaviors that shape how people in an organization interact and work together. Its taught to all new members. Leader show the example.
20
Q

What effect does organizational culture has on project management?

A

Organizational culture has significant effects on projects and project management
- Departmental interaction
- Communication and transparency
- Incentives and motivation
- Office layout design and perks
- Leadership styles
- Chemistry between people
- Employee commitment to goals
- Project planning
- Performance evaluation

21
Q

How projects are selected ?

A

Project selection based on business value
• Each project is measured in terms of business value
• Business value = revenue potential (in most cases)
• Projects with highest business value for the company, considering all resource investments needed, go first

Project selection based on necessity
• Every business has
-A legacy
-Ongoing processes, operations that also need maintenance

Many projects aim at:
- keeping things in the way they are
- improving something in the business operations
- repairing things that broke

22
Q

Factors that influence project selection

A

2 main considerations that drive project selection

Two Main Considerations for Project Selection:
• Technical Feasibility (How easy is it?):
• Determines if the project can be realistically executed based on available technology, resources, and expertise.
• Commercial Potential (Why do it?):
• Evaluates the project’s value in terms of profit, strategic advantage, or market
competitiveness.

Other Factors
Market Demand
Strategic Opportunity
Environmental Consideration
Social need
Customer request
Technological Advance
Legal Requirement

23
Q

Scoring models for project selection:

A

Simplified Checklist model and Simple Scoring model

Using scoring models for project selection
• Scoring is a common model among business decision-making tools
• Scoring is done in game theory or idea selection steps in Design Thinking workshops
They are often used when multiple important criteria exist:
1. Identify potential Criteria
2. Determine mandatory Criteria
3. Weight all Criteria
4. Evaluate projects (based on criteria)
5. Sensitivity analyses

Simplified checklist model:
Projectos > criteria > performance on criteria

Simple scoring model:
Importance weight of criteria > projects > importance weight > score > weighted score

24
Q

Which are the uncertainty influence factors?

A

Screening and selection issues

1. Risk, unpredictability to the firm
a. Technical
b. Financial
c. Safety
d. Quality
e. Legal exposure

2. Commercial, market potential
a. Expected retum on investment
b. Payback period
c. Potential market share
d. Long term market dominance

3. Internal operating, changes in firm operations
a Change in physical environment
b change in manufacturing operations

4. Additional
a. Patent protection
b. Impact on companys image
c. Strategic fit
All models only partially reflect reality and have both objective and subjective factors imbedded

25
Q

Reasons for project failures

A

• Not enough resources
• Not enough time
• Unclear expectations
• Changes to the project
• Disagreement about expectations

26
Q

Difference between plan driven and agile project approaches

A

Plan-Driven is structured, with a focus on completing pre-defined tasks efficiently.
Agile is flexible, encouraging adaptability, teamwork, and continuous improvement.

Plan-Driven Approach:
1. Team Members: Specialists who are part of the team only for the duration of the project.
2. Team Characteristics: Emphasizes high-performing attitudes and behaviors, often focused on predefined roles and tasks.
3. Team Involvement in Planning: Each team member contributes to their specific part of the overall plan.
4. Key Thoughts: Focused on meeting predetermined goals like scope, schedule, and budget.
5. Team Development: Builds skills and sets rules to ensure individual and team performance.
6. Team Responsibilities: Individuals work independently on their assigned tasks.

Agile Approach:
1. Team Members: Generalists or specialized team members with long-term involvement in the team.
2. Team Characteristics: Promotes collaboration, innovation, and adaptability.
3. Team Involvement in Planning: Planning is ongoing and collaborative, with constant adjustments.
4. Key Thoughts: Values simplicity, change readiness, and frequent feedback.
5. Team Development: Encourages knowledge of the product, teamwork, and flexibility.
6. Team Responsibilities: Team members collaborate, ask questions, and support one another to make decisions.

27
Q

Project scope:

A

Project scope is everything about a project - work content as well as expected outcomes.

Project scope defines the boundaries of a project, including the work required (tasks and activities) and the expected outcomes (deliverables). It ensures clarity, prevents unnecessary work, and measures project success.

28
Q

Project scope: What is SOW?

A

Statement of work:

A SOW is a detailed narrative description of the work required for a project.
Effective SOWs contain:
1. Introduction and background
2. Technical description of the project
3. Timeline and milestones

29
Q

Function of scope management

A

Scope Management is the function of controlling a project in terms of its goals and objectives and consists of:

  1. Conceptual development
  2. Scope statement
  3. Work authorization
  4. Scope reporting
  5. Control systems
  6. Proiect closeout
30
Q

What is User Story

A

A user story describes a software feature from the user’s perspective, explaining what they need and why.

Nowadays, common practice in most agile teams in software development is user stories.
“A user story is an informal, general explanation of a software feature written from the perspective of the end user or customer”

Ejemplo: As a customer, I want to be able to cancel my reservation from the app so that I wont lose time in a phone call to do it

31
Q

What is a Risk?

A

Project Risk is anything that may impact the project team’s ability to achieve the general project success measures and the specific project stakeholders’ priorities.

Threat is “a risk that will have a negative impact on the project objective if it occurs.”
- Practice Standard for Project
Risk Management (PMI)

Opportunity is “a risk that would have prostie setiton one or
- Practice Standard for Project
Risk Management (PMI)

32
Q

How you measure risk: Metrics

A

Risk = (Probability of Event)*(Consequences of Event)

33
Q

Categories of risks factors :
Categories and definitions of risk factors

A

A “known-known” can be planned and managed with certainty.
“Known-unknowns” can be identified and may or may not happen.
“Unknown-unknowns” are true uncertainties.

34
Q

What’s risks management and what are the stages?

A

Risk management is identifying, analyzing and responding to risk factors throughout the project and in the best interests of its objectives.

4 stages of risk management:
1. Risk identification
2. Analysis of probability with consequences
3. Risk mitigation strategies
4. Control and documentation

35
Q

Common Types of Risks in Projects

A

General
-Financial
-Legal
-Technical
-Commercial

Common
Absenteeism
Resignation
Staff pulled away
Time overruns
Skills unavailable
Ineffective training
Specs incomplete
Change orders

36
Q

Project Budgeting or Estimation

A

Project cost estimation and budgeting is similar to creating a business plan

Project budgeting at times seems to be an almost impossible undertaking
If you asked an honest answer, most business angels would say they don’t even look business plans because they almost never turn out the way they planned.
Principal-agent theory allows two assumptions (that you can observe in practice):
1. Agent estimates the cost very low in order to get the funds or project approved
2. Agent applies a worst-case cost calculation in order not to be responsible for false estimations

Project cost estimation is like making a business plan-often inaccurate and challenging.
According to the Principal-Agent Theory:
1.Agents might underestimate costs to get approval.
2. Agents might overestimate costs to avoid blame for wrong estimates.

37
Q

Problems by Estimating Cost Projects

A

Project cost estimation issues

Supporting detail (includes describing the scope, method used to create the estimate, assumptions, constraints, and range of possible outcomes)
Causes of variation (e.g., productivity of team members, technical malfunctioning etc.)
Vendor bid analysis (used to determine whether the price being asked by the vendors appears to be reasonable)
Value genering tore quang or petired approach to reducing cost
Time value of money
• International currency flunctuations

Details: Clearly define scope, assumptions, and methods.
Variations: Acount for changes like team productivity orted
Vendor bids: Check if vendor prices are fair.
Value engineering: Reduce costs without lowering quality
Time value of money: Money’s value changes over time
Currency fluctuations: Exchange rates can impact costs.

38
Q

Resource Management and estimating resource needs

A

Resource management: main considerations
Projects have trade-offs between time, resources, cost, and quality.
Resources are limited, and project managers must recognize resource limitations to prevent overpromising
Resource availability, specifically human resources, is a major constraint for projects: People often constitute a large portion of the total project cost

• Resources (like people, tools, and materials) are limited, so managers must plan carefully.
• Human resources are often a major constraint since people are a big part of project costs.

Estimating resource needs
• Managers need to identify and measure the resources required for each task

39
Q

How can schedules be constrained:

A

The schedule can be constrained in two ways:
- one is based on the activities (scope-constrained schedule)
- or the resource limits (resource-constrained schedule), which may be cost-constrained by budget availability

40
Q

How to deal with resources overloads

A

By using project scheduling software, it is possible to understand where and when overloads occur for each worker. The management is required to solve resource overload issues.
Typical options:
• Reorder activities
• Acquire or borrow additional resources
• Reduce project scope or extend project schedule
• Inform sponsor of severe overloads
• Assign certain activities to other workers
• Split an activity into two activities:
• Perform first part as scheduled
• Delay second part of activity

41
Q

What is Project scheduling

A

Scheduling is part of project planning and is defined as (PMBOK, Project Management Institute):

The identification of the project objectives and the ordered activity necessary to complete the project including the identification of resource types and quantities required to carry out each activity or task.

42
Q
  1. Terms of project scheduling:
A

Project Network Diagram: Any schematic display of the logical relationships of project activities
Path: A sequence of activities defined by the project network logic
Event: A point when an activity is either started or completed
Node: One of the defining points of a network; a junction point joined to some or all of the other dependency lines (paths)

43
Q
  1. Terms of Project Scheduling
A

Predecessors: Those activities that must be completed prior to initiation of a later activity in the network
Successors: Activities that cannot be started until previous activities have been completed. These activities follow predecessor tasks
Blocked: When a task in agile projects is waiting on another task to be completed
Early start (ES) date: The earliest possible date the uncompleted portions of an activity can start
Late start (LS) date: The latest possible date that an activity may begin without delaying a specified milestone

44
Q
  1. Terms of Project Scheduling
A

Forward pass: Network calculations to determine earliest start/earliest finish for an activity through working forward through each activity in network
Backward pass: Network calculations to determine late start/late finish for uncompleted tasks through working backward through each activity in network
Critical path: the longest path from end to end which determines the shortest project
Resource-limited schedule: Start and finish dates reflect expected resource availability