Project
A project is a temporary endeavor undertaken to create a unique product, service, or result.
Project Manager
the person assigned by the performing organization to lead the team that is responsible for achieving the project objectives.
Project Attributes
*Time Frame: Definite beginning an end. Work backwards from end date
*Purpose: Create something unique and measurable
*Ownership: A project can have many stakeholders that include people, groups, or other organizations that have a vested interest in the p
Project Roles
?Project Manager or Leader
?Project Sponsor
?Subject Matter Experts (SME)
?Technical Experts(TE)
Project Manager or Leader
The project manager or team leader is responsible for ensuring that all the project management processes and processes associated with the creation of the product, service, or system are in place and carried out efficiently and effectively.
Project Sponsor
The project sponsor may be the client, customer, or high-level executive who plays the role of champion for the project by providing resources, making project-related decisions, giving direction, and publicly supporting the project when needed.
Subject Matter Expert
A subject matter expert may be a user or a person who has specific knowledge, expertise, or insight in a specific functional area needed to support the project.
Technical Experts
Technical expertise is needed when engineering or building a product, service, or system. Technical experts may include database analysts, network specialists, engineers, programmers, graphic artists, and so forth.
Internal Risks
Risks may arise from the way the project work is estimated to cost or the time to be completed.
External Risks
Risks that could arise from dependencies on other contractors, project teams, or suppliers.
Assumptions
Different forms of risk that are introduced to the project as a result of forecasts or predictions.
Progressive Elaboration
The details of a project become clearer as more information becomes available
Project Management
Application of knowledge, skills, tools, and techniques to project activities to meet project requirements.
Project Portfolio
Collection of diverse projects for an organization
Program
Projects are managed where the projects' activities are coordinated so that the benefits of the program are greater than the sum benefits of the individual projects
Why Projects Fail
*People
*Process
*Technology
*Organization
Improving Likelihood of Success
*Value-Driven Approach
*Socio-Technical Approach
*Project Management Approach
*Resources
*Expectation
*Competition
*Efficiency and Effectiveness
*Knowledge Management Approach
Project Methodologies
Provide a systematic way to plan, manage, and execute the work to be completed by prescribing phases, processes, tools, and techniques to be followed.
Benefits of Following a Project Management Methodology
?A project team can focus on the product or system without having to debate how the work is to be done.
?Stakeholders understand their role, and these roles can be applied to future projects.
?Experiences can be documented in terms of lessons learned and
Phase exits, stage gates, or kill points
Phase-end reviews that allow the organization to evaluate the project's performance and to take immediate action to correct any problems or even cancel the project..
Fast tracking
Starting the next phase before the current phase is complete to reduce the project's schedule, but the overlapping of phases can be risky.
Project Life Cycle
*Define Project Goal
*Plan Project-Objectives, Resources, Controls
*Execute Project Plan
*Close and Evaluate Project
*
Project Management Knowledge Areas(PMBOK)
?Project integration management�Integration focuses on coordinating the project plan's development, execution, and control of changes.
?Project scope management�A project's scope is the work to be completed by the project team. This may include specific r
Process
A set of interrelated actions and activities performed to achieve a pre-specified product, result, or service
Project Management Process Groups
?Initiating�The initiating process group signals the beginning of the project or a phase.
?Planning�The planning process group supports planning of the entire project and each individual phase.
?Executing�Once a project phase has been approved and planned
PRojects IN Controlled Environments (PRINCE2 �)
A nonproprietary project management methodology that was developed originally for government projects in the United Kingdom. The aim of PRINCE2 � is to ensure that projects are well-thought out in the beginning, well-managed throughout, and organized unti
Project Board
Managing, monitoring, and controlling the project activities to ensure that the project achieves the value envisioned in the business case. The Project Board may have up to eight people and includes three important roles: a customer, a senior user, and a
Customer
A customer, client, or executive sponsor who represents the business interests of the organization. (PRINCE2)
Senior User
Senior user represents the interests of the users or stakeholders who will use the project's product in order to bring the expected value or benefits to the organization.(PRINCE2)
Senior Supplier
The senior supplier represents the suppliers or specialists who provide the skills or resources needed to deliver the project's product. (PRINCE2)
PRINCE 2 Processes
*Start Project: Focused on developing a project brief or document that provides business justification for the project. The Project Board is created and determines whether the project should be commissioned to continue to the next stage.
?Initiate Project
Work Packages (PRINCE2)
Products to delivered, the people authorized to do the work, constraints, tolerances, as well as the resources and time line for completing the work. This process ensures that the work packages are developed, delivered, and approved as planned.
PRINCE2 Themes
?Business Case: "Why should this project be funded?" and "Why should this project continue to be funded?"
?Organization�"Who is involved with the project?" Under this theme, roles, responsibilities, and accountabilities are defined.
?Quality: Ensure that
PRINCE2 Principles
?Business Case Driven�The business case is a key document that is developed at the beginning of the project and must be continually justified throughout(funding) ?Product Focus�Projects are undertaken to produce a product. PRINCE2 � projects emphasize the
Systems Development Life Cycle (SDLC)
?Planning: Identifying and responding to a problem or opportunity and incorporates the project management and system development processes and activities. Ensures that the goal, scope, budget, schedule, technology, and system development processes, method
PLC v. SDLC
Project life cycle (PLC) focuses on the phases, processes, tools, knowledge, and skills for managing a project.
Systems development life cycle (SDLC) focuses on creating and implementing the project's product�the information system.
Waterfall Model
The waterfall model is a sequential (non-iterative) design process, used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of conception, initiation, analysis, design, construc
Agile Systems Development-Agile Manifesto
Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
12 Principles of Agile Software
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.
Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
Deliver working s
eXtreme Programming
The system is transferred to the users in a series of versions called releases. A release may be developed using several iterations that are developed and tested within a few weeks or months. Each release is a working system that includes only one or seve
User Story
Activities where the user requirements are first documented
Class Diagram
Illustration of the relationships and source code dependencies among classes in the Unified Modeling Language (UML). In this context, a class defines the methods and variables in an object, which is a specific entity in a program or the unit of code repre
Scrum
Scrum is an agile software development model based on multiple small teams working in an intensive and interdependent manner.
Scrum Master
A scrum master is the facilitator for an agile development team. Scrum is a methodology that allows a team to self-organize and make changes quickly, in accordance with agile principles. The scrum master manages the process for how information is exchange
Product Manager
The Scrum product owner is typically a project's key stakeholder. Part of the product owner responsibilities is to have a vision of what he or she wishes to build, and convey that vision to the scrum team. This is key to successfully starting any agile so
Development Team
The Development Team is responsible for delivering potentially shippable increments (PSIs) of product at the end of each Sprint (the Sprint goal). A team is made up of 3-9 individuals who do the actual work (analyse, design, develop, test, technical commu
Product Backlog
Backlog refinement (once called backlog grooming) is the ongoing process of reviewing Product Backlog Items and checking that they are appropriately prioritised and prepared in a way that makes them clear and executable for teams once they enter Sprints v
Sprint
Each sprint generally takes a few weeks, and a completed product is delivered. Additional features and functionality are planned for the next sprint until all of the features in the product backlog are delivered.
Daily Scrum
Each day, the Scrum master, product owner, and development team have a short, stand-up meeting called the daily Scrum during which information and the project's progress are shared.
Learning Cycle and Lessons Learned
*Understand and frame the problem�It is important that a project team not accept the issues and challenges presented to them at face value.
*Plan�To help teams understand and reframe the problem, teams should create a shared understanding of the problem o
Learning Cycle and Lessons Learned Post Mortem Questions
?What do we know now that we didn't know before?
?Have we encountered any surprises? Have we gained any new insights? If so, what were they?
?What previous assumptions have been supported or refuted by what we have learned so far?
?How does the team feel
Three Dimensions to Team Learning
?Speed�First, a team should follow a learning cycle approach rather than a traditional, linear approach. Second, speed refers to the number of learning cycles completed.
?Depth�Depth of learning refers to the degree to which a team can deepen its understa