CBT Project Plus Notes
1. Project: temporary endeavor undertaken to create a unique product, service or result.
Generally, this means creating business value or driving change
2. Project management: is the application of knowledge, skills, tools and tech- niques to
protect activities to meet project requirements.
3. Discovery/concept preparation
Activities in this phase include...: Return on investment (ROI) analysis Preparing the
Business Case
Seeing what vendors or contracts we already have in place which we could utliise Looking at
high level budgets.
4. Initiation
Activities in this phase include...: Identifying stakeholders Reviewing existing
artifacts..
Developing the project charter.
5. Planning
Activities in this phase include...: Activities in this phase includes., Identifying units of
work
Determine the budget
Assigning resources
Developing a schedule
6. Execution
Activities in this phase include: Tracking and reporting on project work Managing
changes
Updating the plan
Exercising soft skills
7. Closing
Activities in this phase include: When the work is formal accepted and final sign off
Handing over to operations
Closing contract Documenting
lessons learned Organizing a
celebration
8. Product life cycle: the entire evolution of a product from concept through retire- ment.
9. Project Life cycle: the series of phases that a project goes through from its start to finish... You
can always go back and visit actives from other phases!!
10.Program: related projects managed in a coordinated manner
11.Portfolios: projects and programs managed in a coordinated way to achieve the
organizations strategic objectives.
12.Program management: focuses on interdependence between projects
, CBT Project Plus Notes
13.Portfolio management: is the strategic view of whether projects or programs align with the
organizations objectives.
14.Waterfall/Predictive approach: Gather all requirements, Design, Plan, Build, test and then
open.
Useful when all requirements can be gathered up front and aren't likely to change. Changes are
discouraged, only changes essential to project are allowed.
15.Cons of Waterfall/Predictive approach: Customer sees no value until the end, and technology
changes all the time.
It isn't good for software development projects which are always changing.
16.Agile Overview: The principle of software development based on iterative and incremental
development.
We work in cycles, and they are often only few weeks each for each cycle. We do just
enough planning, building and testing to test each iteration.
It is also easy to change direction very easily, and make adjustments as we go along. There is
working software at each iteration meaning you can feedback from con- sumers.
Also called Adaptive approach.
17.Manifesto for Agile Software Development: We value.. Individuals
and interactions over processes and tools. Working software over
comprehensive documentation Customer collaboration over contract
negation
And Responding to change over following a plan.
18. 12 Principles of Agile
1-3: 1) Highest priority is to satisfy the customer through early and continuous delivery of
valuable software.
2) Welcome changing requirements even late in development. Agile process har- ness change
for the customers compete advantage
3) Deliver working software frequently from a couple of weeks to a couple of months with a
preference to the shorter timescale.
19. 12 Principles of Agile
4-6: 4) Business people and developers must work together daily throughout the project
5) Build projects around motivated individuals. Give them the environment and support
then need and trust them to get the job done.
6) The most efficient and effective method of converting information to and within a
development team is face to face conversation.
20. 12 Principles of Agile
7-9: 7) Working software is the primary measure of progress.
8) Agile processes promot sustainable development. The sponsors, developers and
, CBT Project Plus Notes
users should be able to maintain a constant pace indefinitely.
9) Continuous attention to technical excellence and good design enhances agility.
21. 12 Principles of Agile
10-12: 10) Simplicity the art of maximizing the amount of work not done, its essential.
11)The best architectures, requirements and designs emerge from self organizing teams.
12) At regular intervals the team reflects on how to become more effective, then tunes and
adjusts the behavior accordingly.
22.Selecting an approach Environmental factors: what's our company culture or structure, what's
generally expected in the industry? Is it stable or unpredictable?
23.Selecting an approach Schedule or Budget Constraints: do we need to deliver value
early?Are we unsure how long funding will be available
24.Selecting an approch Stakeholder expectations: do stakeholders expect day to day
involvement? Or occasional updates?
25.Team members for Scrum: Product owner, developers, scrum master
26. Product owner
Member of Scrum: owns the product that we are building and she the authority
27.Product Backlog: a continually evolving prioritized list of work that needs to be done.
28.developers: <10 than people per team and make sure they are cross functional, and they
are self organized.
29.Scrum Master: facilitator, no manger authority but promoting SCRUM values and removing
obstacles.
30.Sprints: In the short cycles that we work through are called Sprints there are generally a
fixed length of less than a month. A new sprint starts immediately after the conclusion of the
previous one.
31.Sprint planning meeting: Product owner is bringing her product backlog into a meeting with
developer and they together agree on a sprint goal, which is what we are going to achieve in
this particular sprint. They look at backlog and decide which items from towards the top they
can get done in the sprint, which will achieve sprint goal.
32. Sprint planning meeting
Sprint backlog: The development team will further break down each product back- log into
specific tasks. This is the next artifact the sprint backlog.
33. Part of SCRUM
Daily scrum: Daily stand up meeting to enable developer to inspect progress towards the
sprint goal and to make any adjustments to the sprint backlog as required. Is a repeating
activity during the sprint.
1. Project: temporary endeavor undertaken to create a unique product, service or result.
Generally, this means creating business value or driving change
2. Project management: is the application of knowledge, skills, tools and tech- niques to
protect activities to meet project requirements.
3. Discovery/concept preparation
Activities in this phase include...: Return on investment (ROI) analysis Preparing the
Business Case
Seeing what vendors or contracts we already have in place which we could utliise Looking at
high level budgets.
4. Initiation
Activities in this phase include...: Identifying stakeholders Reviewing existing
artifacts..
Developing the project charter.
5. Planning
Activities in this phase include...: Activities in this phase includes., Identifying units of
work
Determine the budget
Assigning resources
Developing a schedule
6. Execution
Activities in this phase include: Tracking and reporting on project work Managing
changes
Updating the plan
Exercising soft skills
7. Closing
Activities in this phase include: When the work is formal accepted and final sign off
Handing over to operations
Closing contract Documenting
lessons learned Organizing a
celebration
8. Product life cycle: the entire evolution of a product from concept through retire- ment.
9. Project Life cycle: the series of phases that a project goes through from its start to finish... You
can always go back and visit actives from other phases!!
10.Program: related projects managed in a coordinated manner
11.Portfolios: projects and programs managed in a coordinated way to achieve the
organizations strategic objectives.
12.Program management: focuses on interdependence between projects
, CBT Project Plus Notes
13.Portfolio management: is the strategic view of whether projects or programs align with the
organizations objectives.
14.Waterfall/Predictive approach: Gather all requirements, Design, Plan, Build, test and then
open.
Useful when all requirements can be gathered up front and aren't likely to change. Changes are
discouraged, only changes essential to project are allowed.
15.Cons of Waterfall/Predictive approach: Customer sees no value until the end, and technology
changes all the time.
It isn't good for software development projects which are always changing.
16.Agile Overview: The principle of software development based on iterative and incremental
development.
We work in cycles, and they are often only few weeks each for each cycle. We do just
enough planning, building and testing to test each iteration.
It is also easy to change direction very easily, and make adjustments as we go along. There is
working software at each iteration meaning you can feedback from con- sumers.
Also called Adaptive approach.
17.Manifesto for Agile Software Development: We value.. Individuals
and interactions over processes and tools. Working software over
comprehensive documentation Customer collaboration over contract
negation
And Responding to change over following a plan.
18. 12 Principles of Agile
1-3: 1) Highest priority is to satisfy the customer through early and continuous delivery of
valuable software.
2) Welcome changing requirements even late in development. Agile process har- ness change
for the customers compete advantage
3) Deliver working software frequently from a couple of weeks to a couple of months with a
preference to the shorter timescale.
19. 12 Principles of Agile
4-6: 4) Business people and developers must work together daily throughout the project
5) Build projects around motivated individuals. Give them the environment and support
then need and trust them to get the job done.
6) The most efficient and effective method of converting information to and within a
development team is face to face conversation.
20. 12 Principles of Agile
7-9: 7) Working software is the primary measure of progress.
8) Agile processes promot sustainable development. The sponsors, developers and
, CBT Project Plus Notes
users should be able to maintain a constant pace indefinitely.
9) Continuous attention to technical excellence and good design enhances agility.
21. 12 Principles of Agile
10-12: 10) Simplicity the art of maximizing the amount of work not done, its essential.
11)The best architectures, requirements and designs emerge from self organizing teams.
12) At regular intervals the team reflects on how to become more effective, then tunes and
adjusts the behavior accordingly.
22.Selecting an approach Environmental factors: what's our company culture or structure, what's
generally expected in the industry? Is it stable or unpredictable?
23.Selecting an approach Schedule or Budget Constraints: do we need to deliver value
early?Are we unsure how long funding will be available
24.Selecting an approch Stakeholder expectations: do stakeholders expect day to day
involvement? Or occasional updates?
25.Team members for Scrum: Product owner, developers, scrum master
26. Product owner
Member of Scrum: owns the product that we are building and she the authority
27.Product Backlog: a continually evolving prioritized list of work that needs to be done.
28.developers: <10 than people per team and make sure they are cross functional, and they
are self organized.
29.Scrum Master: facilitator, no manger authority but promoting SCRUM values and removing
obstacles.
30.Sprints: In the short cycles that we work through are called Sprints there are generally a
fixed length of less than a month. A new sprint starts immediately after the conclusion of the
previous one.
31.Sprint planning meeting: Product owner is bringing her product backlog into a meeting with
developer and they together agree on a sprint goal, which is what we are going to achieve in
this particular sprint. They look at backlog and decide which items from towards the top they
can get done in the sprint, which will achieve sprint goal.
32. Sprint planning meeting
Sprint backlog: The development team will further break down each product back- log into
specific tasks. This is the next artifact the sprint backlog.
33. Part of SCRUM
Daily scrum: Daily stand up meeting to enable developer to inspect progress towards the
sprint goal and to make any adjustments to the sprint backlog as required. Is a repeating
activity during the sprint.
