Module 3: Project Initiation Flashcards
When should an Incremental development approach be used
If you are leading a project where requirements are not well defined, change is expected, and the customer wants several deliveries of useful products
Which of the following is not an accountable unit in the scrum framework?
Product manager
Scrum master
Development team
Project owner
Product manager
Customer request
A description of what a customer or user would want from a product or solution
Iterative approach
Used with feedback is needed on a regular basis. Final product not delivered until it has undergone a few iterations.
Incremental approach
Builds on previous one. Complete one small part before moving onto next.
Repeats planning and executing for each increment
User stories
written in a way to be clear whether the team is using iterative or incremental approach
Product lifecycle
include one or more projects that can start at any point during the product life cycle
Phases of adaptive/agile development
Start with design phase and includes 3 iterations. Feedback and backlog prioritization is done after each iteration
Gate meeting
done prior to each phase to determine whether it should go ahead or not.
Scrum
Complex or innovative projects.
To use an analogy, think of Agile as a diet and Scrum as a type of diet
Product Backlog
This contains a prioritized list of work that needs to be done.
Sprint Backlog
During the planning stage, the project team takes an item from the product backlog and creates the sprint backlog.
Sprint
The project team will have 2-4 weeks to complete this work.
Daily Scrum Meeting
Each day the project team meets to discuss progress.
Scrum Master
A Scrum Master is in charge of these meetings and asks questions like:
1) How much has been done since our last meeting.
2) Have there been any problems/obstacles.
3) What will be done for today
Potentially Shippable Product
At the end of the 2-4 weeks the product should be completed and ready for the client’s inspection.
Pre-initiating processes
1) approval through a formal selection process.
2) Determine scope, time, and cost constraints for the project.
3) A business case
4) PM selected.
5) The project process and expectations need to be discussed with PM.
6) identify stakeholders
7) create project charter
8) Kick-off meeting
Business case components
- Justification for investing
- cost-benefit analysis
Components of stakeholder registry
name, position, location, role in project, internal/external, whether they support project or not, requirements.
Stakeholder analysis
shows their interest and level of authority
Project charter
establishes formal existence of project. High level information
- objectives
-goals
-stakeholders
- constraints
- risks
-budget
Formal authorization to begin project and authority to use resources
SOW
statement of work
Identifies business need, scope, organization’s strategic vision, goals, and objectives.
Key stakeholders in Agile project
Product Owner (client, manager): Responsible for maximizing the value of the product
Scrum Master (PM): Responsible for promoting and supporting the Scrum process
Development Team: These are the professionals who do the work to complete the deliverables during each sprint.
Vision statement
Describes the desired future state that would be achieved by developing and deploying a product.
Product Release Plan:
It is a process of deciding which features of the project will be offered in which release.
User story
This is a description of what a customer or user would want from a product or solution.
Format: As a < type of user >, I want < some goal > so that < some reason >.
Product Backlog:
Product owner creates
-ordered and evolving list of what is needed to improve the product. This list is actually a list of user stories.
Product Strategy
high-level plan (roadmap) describes what the organization hopes to accomplish with its product and how it plans to do so. The roadmap contains a prioritization list of business goals.
