Unit-5 Agile
Unit-5 Agile
SYLLABUS
Risks in Agile Project Management
Agile Project Management: Best Practices and
Methodologies
Capital Costs and Budgeting
Agile QA Process: Principles, Steps, and Best
Practices
2
RISKS IN AGILE PROJECT
MANAGEMENT
Risk is any unexpected event that can affect your project
It is different from issues, eg: An Employees’s vacation is an issue
and you know how to handle it
Example for risk is Flu season hitting your team, key product componen
Being on backorder
What risks exist for the client using Agile/Scrum?
1. Budget Risks – Solution: Lean Development, Rolling Wave Planning
2. Scope creep risk- Solution:Splitting Dev into MVP1.0, 1.1…..
3. Not sticking with agile principles- Solution: teach and Monitor Agile
4. Less predictability- Solution: Clarify Reuiremnts in detail
What risks exist for the vendor using Agile/Scrum?
5. Lack of Staff Knowledge- Sol:Constant retrospective meetings
6. A sudden stop of work – Sol:conduct discovery phase to learn more about product
7. Technical debt-Soleach user story or task has its own acceptance criteria
and definition of done
As defined by Gartner, project management is “the application of knowledge, skills, tools, and
AGILE PROJECT MANAGEMENT: BEST PRACTICES AND METHODOLOGIES
Value of teamwork: The team members work closely together and have a clear vision of their
responsibilities.
Iterative improvements: There is a frequent reassessment of the work done within a cycle to make
the final product better.
Cooperation with a client: A customer is closely engaged in the development and can change the
requirements or accept the team’s suggestions.
CAPITAL COSTS AND BUDGETING
The Agile methodology has emerged as a game-changer in this pursuit, offering a flexible
and adaptive approach to project management
An Agile budget is a dynamic and flexible financial plan that aligns with the iterative
nature of Agile project management
In the Agile world, budgeting is a continuous and collaborative process, involving cross-
functional teams and stakeholders
6
PRINCIPLES OF AGILE QA
Test early and often Automate what you can, but don’t automate
The “shift left” approach, involving QA early everything
in development and fostering mutual Automation is essential to agile QA, but it still
understanding between QA and development has costs and should not be done willy-nilly
teams, cultivates a shared drive for higher with no strategy. It’s important to automate
product quality. parts of testing that take time and are tedious,
Provide continuous feedback and open but that doesn’t mean that manual testing
communication should be removed from the process entirely.
7
CHANGE CONTROL
Change control is the process through which all requests
to change the approved baseline of a project, program • Change management is baked into the
or portfolio are captured, evaluated and then approved, Agile approach
rejected or deferred. • There is a Change Control Board
Top 7 Change Control Process Tools: • Change requests are received and
evaluated
7. Monday.com
8
THANK YOU