Final Project Submission: Advanced Scrum Project Management Objective: To expand upon the initial project submitted earlier in the term by applying advanced S
MGMT 642: Agile Project Management (HBD-SUMMER24-07)
Final Project Submission: Advanced Scrum Project Management
Objective: To expand upon the initial project submitted earlier in the term by applying advanced Scrum practices covered in Chapters 1, 5, 6, 7, 8, 9, and 12 of "Project Management the Agile Way." This final submission requires comprehensive project management using Scrum principles, documented in JIRA and Confluence, with screenshots demonstrating the completion of each section.
Project Overview: This final project is a continuation and refinement of the initial Scrum project your group submitted in the first half of the term. You will enhance your initial work by incorporating advanced Scrum practices, focusing on refining the product backlog, sprint planning, estimation, team dynamics, governance, and transitioning strategies.
Project Tasks:
- Refinement of the Product Backlog (Chapters 1 & 5):
- A. Review and refine the product backlog from your initial submission. Ensure user stories are clear, concise, and follow the format: “As a [user], I want [functionality], so that [benefit].”
- B. Prioritize user stories using the MoSCoW method (Must have, Should have, Could have, Won't have this time). Ensure the product backlog is organized based on business value, risk, and dependencies.
- **C. Add acceptance criteria to each user story to define the conditions of satisfaction.
- Document: Record all refined user stories and acceptance criteria in Confluence.
- Screenshots Required: Updated product backlog from JIRA, showing user stories, priorities, and acceptance criteria.
- Sprint Planning and Sprint Backlog Creation (Chapter 6):
- A. Conduct a sprint planning session to define the sprint goal and select user stories from the product backlog for the upcoming sprint.
- **B. Break down selected user stories into actionable tasks and create a sprint backlog in JIRA.
- **C. Estimate tasks using Scrum estimation techniques such as Planning Poker and Story Points.
- Document: Outline the sprint planning process, sprint goal, selected user stories, and estimated tasks in Confluence.
- Screenshots Required: Sprint backlog, task board, and estimation details from JIRA.
- Burndown Charts and Sprint Reviews (Chapter 7):
- A. Track progress using a burndown chart in JIRA. Monitor the completion of tasks and user stories throughout the sprint.
- **B. Conduct a sprint review at the end of each sprint to demonstrate the work completed and gather feedback from stakeholders.
- Document: Summarize the sprint review outcomes and any feedback received in Confluence.
- Screenshots Required: Burndown chart and sprint review board from JIRA.
- Team Dynamics and Retrospectives (Chapter 8):
- A. Reflect on team dynamics throughout the project. Assess areas such as trust, collaboration, and communication within the team.
- **B. Conduct a sprint retrospective at the end of each sprint to identify what went well, what could be improved, and actionable steps for future sprints.
- Document: Record the findings and action items from each sprint retrospective in Confluence.
- Screenshots Required: Retrospective board and team performance charts from JIRA.
- Governance and Scrum Roles (Chapter 9):
- A. Define the governance framework for your Scrum project, including the roles of the Product Owner, Scrum Master, and Development Team.
- **B. Outline the decision-making processes and conflict resolution strategies within the team.
- **C. Identify key risks to the project and develop a risk mitigation plan using JIRA.
- Document: Describe the governance framework, roles, and risk management strategies in Confluence.
- Screenshots Required: Risk register and role assignments in JIRA.
- Transition Strategy and Continuous Improvement (Chapter 12):
- A. Develop a transition strategy for moving from your current project state to a fully Agile Scrum framework, if not already implemented.
- **B. Outline a plan for continuous improvement, focusing on how your team will regularly assess and adapt Scrum practices.
- Document: Detail the transition strategy and continuous improvement plan in Confluence.
- Screenshots Required: Transition plan and improvement strategy board in JIRA.
Submission Requirements:
- Format: Compile all documentation into a single PDF file, including screenshots from JIRA and Confluence for each section.
- Screenshots: Ensure all screenshots are clear and demonstrate the completed sections of the project in JIRA and Confluence.
Assessment Criteria:
- Completeness and clarity of the refined product backlog and user stories.
- Effectiveness of sprint planning and backlog creation.
- Accurate use of Scrum estimation techniques and burndown charts.
- Insightful analysis of team dynamics and constructive retrospectives.
- Robustness of governance framework and defined Scrum roles.
- Practicality and effectiveness of the transition strategy and continuous improvement plan.
- Proper use of Scrum tools (JIRA and Confluence): Demonstrated through comprehensive screenshots and documentation.
Suggested Resources:
- JIRA and Confluence tutorials and guides.
- "Project Management the Agile Way" Chapters 1, 5, 6, 7, 8, 9, and 12.
- Additional Scrum and Agile resources.
History, Background, and the Manifesto
Modern projects are constrained by several uncertainties
Limitations of Traditional Project Management
1
History, Background, and the Manifesto
handle difficult situations,…….. people
Limitations of Traditional Project Management
2
History, Background, and the Manifesto
It is difficult to change the plan once it is baselined
Limitations of Traditional Project Management
3
History, Background, and the Manifesto
End users see the end product only at the end of the project.
Limitations of Traditional Project Management
4
Traditional Life Cycle
Predictable outcomes arising from up-front plans and specifications, enforced by change management
J. Ross Publishing WAV™ material JR1157- 00_Instructor's Guide 5
PDLC (project Development Life Cycle)
Plan-Driven Lifecycle
Simple and intuitive High ceremony
process, metrics and
documentation
Role of the customer in PD- PDLC ( at arms
length)
however, need to do a lot of
work)
PD-PDLC advantages and disadvantages
JR1157- 00_Instructor'
s Guide J. Ross Publishing WAV™ material 6
build and deliver the specified outcomes according to a master project plan
Plan-Driven Lifecycle
Business opportunity
Simple and intuitive
High ceremony ( process, metrics and documentation)
Role of the customer in PD-PDLC ( at arms length, however, need to do a lot of work)
PD-PDLC advantages and disadvantages
7
Advantage
Fits large and very large projects,
Does not depend on an exceptionally
talented workforce
Lots of tool support
Large, trained base of
practitioners
Intuitively simple to
understand
Rich with reporting, as
usually implemented
Plan-Driven Lifecycle
Business opportunity
Simple and intuitive
High ceremony ( process, metrics and documentation)
Role of the customer in PD-PDLC ( at arms length, however, need to do a lot of work)
PD-PDLC advantages and disadvantages
JR1157- 00_Instructor'
s Guide J. Ross Publishing WAV™ material 8
Disadvantage
Inappropriate where
requirements cannot be fixed,
or where customer changes are
frequent
Inappropriate for small teams, with
fewer than 25 developers
Delivery of business value is
late in the lifecycle
Changes coming late are very expensive to
insert
Heavy, expensive, process and
documentation,
requires governance formality
Agile means getting effective project results
even in complex and uncertain
project requirements,
primarily by
applying small teams—
working collaboratively—
to deliver frequently
increments of business value,
with priority according to
effectiveness, importance, and urgency
9
Agile Manifesto
Agile Principles
Commentary on the 12 Principles
Other Agile principles
JR1157- 00_Instructor'
s Guide J. Ross Publishing WAV™ material 10
Agile Manifesto
Agile Principles
Commentary on the 12 Principles
Other Agile principles
JR1157- 00_Instructor'
s Guide J. Ross Publishing WAV™ material 11
Agile Lifecycle
Strategically stable, but tactically emergent, iterative, and incremental
J. Ross Publishing WAV™ material JR1157- 00_Instructor's Guide 20
Agile Lifecycle
Strategically stable, but tactically emergent, iterative, and incremental
J. Ross Publishing WAV™ material JR1157- 00_Instructor's Guide 21
Agile Methodologies
Management simplicity, process discipline, personal safety, and measurable progress
J. Ross Publishing WAV™ material JR1157- 00_Instructor's Guide 22
Agile Methodologies
Management simplicity, process discipline, personal safety, and measurable progress
J. Ross Publishing WAV™ material JR1157- 00_Instructor's Guide 23
Scrum
Team members
Scrum master
Product owner
Product backlog
Scrum
Sprint review
Daily scrum
Sprint backlog
User Story
Product backlog
Agile Lifecycle
An Agile manager’s agenda
Guiding principles for Agile managers
Addressing the major risks
J. Ross Publishing WAV™ material JR1157- 00_Instructor's Guide 28
Agile Lifecycle
An Agile manager’s agenda
Guiding principles for Agile managers
Addressing the major risks
JR1157- 00_Instructor'
s Guide J. Ross Publishing WAV™ material 29
• Customers: Coach customers’ and end-users’
• Encourage communications that are open, honest, and real time
• Results: Maintain a focus on results, not specifically on process and activity
• People: Internalize the idea things are managed; people are led
• Champion innovation and technical excellence
An Agile manager’s agenda
Agile Lifecycle
An Agile manager’s agenda
Guiding principles for Agile managers
Addressing the major risks
JR1157- 00_Instructor'
s Guide J. Ross Publishing WAV™ material 30
• Plans are adaptive.
• Value is the privilege of customers
• Schedule and cost are derived
• Change is embraced and encouraged: • • Documentation comes after personal interaction
• Individuals are trusted
Guiding principles for Agile managers
Agile Lifecycle
An Agile manager’s agenda
Guiding principles for Agile managers
Addressing the major risks
JR1157- 00_Instructor'
s Guide J. Ross Publishing WAV™ material 31
Addressing the Major Risks Agile methods address the major risks of the traditional methodology that are blamed for poor product quality and poor project performance.
• BDUF: Agile makes no attempt to do a big design up front
• Unknown or unknowable requirements: Customers are allowed to add, delete, revise, and reprioritize requirements at the beginning of each iteration, but not during an iteration.
• Customers at arm’s length: Customers are included s and coached
• Testing and delivery is all at the end of the project cycle
• Documentation is not cost effective: Documentation is minimized …documentation is replaced by daily collaboration and informal means to communicate: e-mail, instant messages, comments em-bedded in the product design, story cards, scorecards, and dashboards.
Module 5 Outline
Representative Agile Methods
Methodologies compared
A process of cycles
Advantages and Disadvantages of Agile
JR1157- 00_Instructor'
s Guide J. Ross Publishing WAV™ material 32
Representative Agile Methods
Methodologies compared
A process of cycles
Advantages and Disadvantages of Agile
JR1157- 00_Instructor'
s Guide J. Ross Publishing WAV™ material 33
- �History, Background, and the Manifesto�
- �History, Background, and the Manifesto�
- �History, Background, and the Manifesto�
- �History, Background, and the Manifesto�
- Traditional Life Cycle��
- PDLC (project Development Life Cycle)
- Slide Number 7
- Slide Number 8
- Slide Number 9
- Slide Number 10
- Slide Number 11
- Slide Number 12
- Slide Number 13
- Slide Number 14
- Slide Number 15
- Slide Number 16
- Slide Number 17
- Slide Number 18
- Slide Number 19
- �Agile Lifecycle��
- �Agile Lifecycle��
- Agile Methodologies�
- Agile Methodologies�
- Scrum
- Slide Number 25
- Scrum
- Slide Number 27
- Slide Number 28
- Slide Number 29
- Slide Number 30
- Slide Number 31
- Module 5 Outline
- Slide Number 33
,
• Introduction to Agile Project Charters
• Definition and importance of Agile project charters.
### Definition of Agile Methodologies:
• – Agile methodologies involve
iterative and incremental approaches.
• They are characterized by principles like
• flexibility,
• collaboration,
• customer feedback, and
• rapid response to change.
• increasing adoption of Agile methodologies in various industries
### Industries Embracing Agile:
1. **Technology and Software Development:**
• to address the rapidly changing requirements
2. **Marketing and Creative Industries:**
• – to respond quickly to
market trends,
3. **Financial Services and Banking:**
• -for product development
• and to comply with rapidly changing regulations.
4. **Manufacturing:**
• – for product development
5. **Healthcare:**
• – managing complex projects,
Agile Project Charter
• is: “a brief document that
defines the scope,
objectives, and
participants of a project."
• unlike traditional project charters, Agile charters are less about detailed project plans and more about a clear vision and direction.
3. **Importance of Agile Project Charters:**
• "serve as a guiding light for Agile teams
• facilitate flexibility within the defined scope
• help in managing stakeholders'
expectations.
Steps:
1. **Setting Clear but Flexible Goals:**
• – outline the project's goals in a
broad sense.
• – By setting clear objectives without
being overly prescriptive about how to achieve them
**Project Example:** Mobile Health Application Development
• **Clear Goal:** Launch a user-friendly mobile app for fitness and diet tracking on multiple platforms within 6 months.
• **Flexibility:**
• – Development methods and technologies can vary.
• – Features will be delivered incrementally,
• – The team remains open to incorporating new user needs and mew technology
2. **Defining Roles and Responsibilities:**
• – This clarity helps team members
understand their scope of work
• decision-making authority, which is essential for fast-paced Agile environments.
– It allows teams to self- organize and make decisions
quickly
3. **Outlining Scope with Room for Adaptation:**
4. **Establishing Stakeholder Engagement and Expectations:**
5. **Emphasizing Continuous Feedback and Improvement:**
In summary,
• They balance the need for direction and understanding that
change is an inherent part of the project lifecycle,
"What to Include in an Agile Project Charter,"
1. **Project Vision and Mission**: • the purpose, objectives, and expected outcomes
Vision
• The vision is not just a statement; it's the project's heartbeat.
• It encapsulates the purpose—why this project matters, not only to us but to our stakeholders and the community it serves.
• Imagine we’re developing a mobile application
aimed at reducing food waste by connecting local retailers with consumers to sell surplus food at discounted rates.
• The purpose of our project is to combat food waste and promote sustainability.
Objectives
• Objectives are our milestones.
• In the agile world, these are not just static targets; they're dynamic, adaptable, and iterative.
• The objectives might include creating • a user-friendly interface,
• developing a robust notification system, and
• implementing a secure payment gateway by the end of the third quarter.
• These are specific targets that can be broken down into user stories and tasks in our backlog.
• They are the stepping stones that we will reassess and refine in each iteration, always with the end goal in sight.
Expected outcomes
• Expected outcomes are the
tangible changes or benefits we foresee.
• These are the real-world manifestations of our work
• Example
• we are looking to enroll 100 local retailers and achieve 10,000 downloads in the first six months post-launch, thereby reducing food waste by 5%.
**Scope of the Project**:
• the boundaries and limitations of the project are defined.
• It includes what is included and, importantly, what is not included in the project, helping to prevent scope creep.
In Scope • Redesign Of User Interface (Ui)
• Content Update
• Mobile Responsiveness
• User Feedback Implementation
Out Of Scope • 1. Back-End Development
• 2. Rebranding
• 3. E-commerce Integration
• 4. Internationalization
3. **Risks and Issues**:
• identifies potential risks and issues that might arise during the project.
• It includes strategies for mitigating these risks and plans for addressing any issues that occur.
**Example of Risks and Issues:**
• 1. **Risk Identification:**
• – **Technical:** Challenges with new software integration.
• – **Resource:** Availability and skill gaps in the team.
• – **Schedule:** Potential delays due to external dependencies.
• – **Market:** Shifts in market conditions affecting project relevance.
• 2. **Risk Mitigation:**
• – **Technical:** Pilot testing new tools, keeping backup options.
• – **Resource:** Cross-training, maintaining a resource pool.
• – **Schedule:** Adding buffer time, regular vendor communication.
• – **Market:** Regular market trend reviews, stakeholder engagement.
4. **Roles and Responsibilities**:
• This section outlines the roles and responsibilities of each team member.
• It helps in establishing clear
accountability and
ensures that everyone understands their role in the project.
### Example:
• 1. **Product Owner (PO):**
• – **Name:** Alex Johnson
• – **Responsibilities:**
• – Defines project goals and priorities.
• – Manages the product backlog.
• – Acts as the primary liaison between stakeholders and the development team.
• – Ensures the team always works on the most valuable features.
• – Accepts or rejects deliverables.
5. **Stakeholders**:
• Identifying the key stakeholders involved in the project is crucial.
• This includes anyone who has an interest in or is affected by the project’s outcomes.
6. **Success Criteria**:
• Defines how the success of
the project will be measured.
• This could include specific project goals, quality standards, or performance metrics.
7. **Communication
Plan**:
• This part covers how communication will be managed throughout the project.
• It includes methods, frequency, and channels of communication among team members and stakeholders.
8. **Budget and Resources**:
• Details the financial and physical resources available for the project.
• It includes the budget allocation and any constraints or limitations regarding resources.
9. **Timeline and Milestones**:
• Outlines the project timeline, including key milestones and deadlines.
• This helps in tracking progress and ensuring the project stays on schedule
- Slide 1
- Slide 2
- Slide 3: ### Definition of Agile Methodologies:
- Slide 4
- Slide 5
- Slide 6: ### Industries Embracing Agile:
- Slide 7: 1. **Technology and Software Development:**
- Slide 8: 2. **Marketing and Creative Industries:**
- Slide 9: 3. **Financial Services and Banking:**
- Slide 10: 4. **Manufacturing:**
- Slide 11: 5. **Healthcare:**
- Slide 12: 6. **Government and Public Sector:**
- Slide 13: Agile Project Charter
- Slide 14
- Slide 15: 3. **Importance of Agile Project Charters:**
- Slide 16
- Slide 17: Steps:
- Slide 18: 1. **Setting Clear but Flexible Goals:**
- Slide 19: **Project Example:** Mobile Health Application Development
- Slide 20: 2. **Defining Roles and Responsibilities:**
- Slide 21: 3. **Outlining Scope with Room for Adaptation:**
- Slide 22: 4. **Establishing Stakeholder Engagement and Expectations:**
- Slide 23: 5. **Emphasizing Continuous Feedback and Improvement:**
- Slide 24: In summary,
- Slide 25: "What to Include in an Agile Project Charter,"
- Slide 26: 1. **Project Vision and Mission**:
- Slide 27: Vision
- Slide 28: Objectives
- Slide 29: Expected outcomes
- Slide 31: **Scope of the Project**:
- Slide 32: In Scope
- Slide 33: Out Of Scope
- Slide 34: 3. **Risks and Issues**:
- Slide 35: **Example of Risks and Issues:**
- Slide 36: 4. **Roles and Responsibilities**:
- Slide 37: ### Example:
- Slide 38: 5. **Stakeholders**:
- Slide 39: 6. **Success Criteria**:
- Slide 40: 7. **Communication Plan**:
- Slide 41: 8. **Budget and Resources**:
- Slide 42: 9. **Timeline and Milestones**:
,
Agile Scope and Requirements
1
Agile scope
2
Evolving, emerging, and adapting Scope as a best value
Agile Scope
u The most important point is that the evolving and emerging scope is managed
J. Ross Publishing WAV™ material JR1157- 00_Instructor's Guide 3
Agile Scope The planning is organized this way
4
The business case holds the product vision in a top-level framework,
Scope is planned incrementally with evolution allowed and encouraged
Planning occurs in shorter frameworks called rolling waves
Development cycles—called iterations or sprints
Agile Scope (A-B-C)
A- Evolving, Emerging, and Adaptive
5
Scope
Schedule
Budget
Quality
Four Levers
Agile Scope
A-1 Best Value
6
customer satisfaction Vs Plan variance
scope is the most flexible
Agile Scope A-1 Best Value
uThe most scope possible— for the available resources—
Agile Scope A-2 Defined
u Scope is
u all the things we must do,
u all the things we want to do,
u all the things we actually do
8
Agile Scope A-3 Backlog
9
• is the scope parsed into • work units, • stories, • use cases, • Tasks
Agile Scope A-4 Architecture
10
• is the scope mapped into • form • function
<div
Collepals.com Plagiarism Free Papers
Are you looking for custom essay writing service or even dissertation writing services? Just request for our write my paper service, and we'll match you with the best essay writer in your subject! With an exceptional team of professional academic experts in a wide range of subjects, we can guarantee you an unrivaled quality of custom-written papers.
Get ZERO PLAGIARISM, HUMAN WRITTEN ESSAYS
Why Hire Collepals.com writers to do your paper?
Quality- We are experienced and have access to ample research materials.
We write plagiarism Free Content
Confidential- We never share or sell your personal information to third parties.
Support-Chat with us today! We are always waiting to answer all your questions.