- Work Breakdown Structure
- Traditional Project Management
- Total Quality Management
- Total Productive Maintenance
- The Virtual Team
- The Rule of Seven
- The Make or Buy Decision
- The Halo Effect
- The Balanced Scorecard
- Team Motivation
- Team Building Program
- Supply Chain Management
- Succession Planning
- Structured Brainstorming
- Stress Management Techniques
- Statement of Work (SOW)
- Stakeholder Management
- Staffing Management Plan
- Resource Leveling
- Requirement Collection
- Recognition and Rewards
- RACI Chart Tool
- QC and QA Processes
- Project Management Softwares
- Project Workforce Management
- Project Time Management
- Project Success Criteria
- Project Selection Method
- Project Scope Definition
- Project Risk Management
- Project Risk Categories
- Project Records Management
- Project Quality Plan
- Project Portfolio Management
- Project Manager Goals
- Project Management Triangle
- Project Management Tools
- Project Management Processes
- Project Management Office
- Project Management Methodologies
- Project Lessons Learned
- Project Kick-off Meeting
- Project Cost Control
- Project Contract Types
- Project Charter
- Project Activity Diagram
- Procurement Management
- Procurement Documents
- Process Based Management
- Powerful Leadership Skills
- Pareto Chart Tool
- PRINCE2 Project Methodology
- PERT Estimation Technique
- Organizational Structures
- Negotiation Skills
- Motivation Theories
- Monte Carlo Analysis
- Management by Objectives
- Management Styles
- Management Best Practices
- Leads, Lags and Floats
- Knowledge Management
- Just-In-Time Manufacturing
- Gantt Chart Tool
- Extreme Project Management
- Event Chain Methodology
- Enterprise Resource Planning
- Effective Presentation Skills
- Effective Communication Skills
- Design of Experiment
- Decision Making Process
- Critical Path Method
- Critical Chain Scheduling
- Crisis Management
- Conflict Management
- Communications Management
- Communication Models
- Communication Methods
- Communication Channels
- Communication Blockers
- Change Management Process
- Cause and Effect Diagram
- Benchmarking Process
- Basic Quality Tools
- Basic Management Skills
- Agile Project Management
- Activity Based Costing
- Project Management Home
Useful Resource
Selected Reading
- Who is Who
- Computer Glossary
- HR Interview Questions
- Effective Resume Writing
- Questions and Answers
- UPSC IAS Exams Notes
Agile Project Management
Introduction
Agile Project Management is one of the revolutionary methods introduced for the practice of project management. This is one of the latest project management strategies that is mainly appped to project management practice in software development. Therefore, it is best to relate agile project management to the software development process when understanding it.
From the inception of software development as a business, there have been a number of processes following, such as the waterfall model. With the advancement of software development, technologies and business requirements, the traditional models are not robust enough to cater the demands.
Therefore, more flexible software development models were required in order to address the agipty of the requirements. As a result of this, the information technology community developed agile software development models.
Agile is an umbrella term used for identifying various models used for agile development, such as Scrum. Since agile development model is different from conventional models, agile project management is a speciapzed area in project management.
The Agile Process
It is required for one to have a good understanding of the agile development process in order to understand agile project management.
There are many differences in agile development model when compared to traditional models:
The agile model emphasizes on the fact that entire team should be a tightly integrated unit. This includes the developers, quapty assurance, project management, and the customer.
Frequent communication is one of the key factors that makes this integration possible. Therefore, daily meetings are held in order to determine the day s work and dependencies.
Depveries are short-term. Usually a depvery cycle ranges from one week to four weeks. These are commonly known as sprints.
Agile project teams follow open communication techniques and tools which enable the team members (including the customer) to express their views and feedback openly and quickly. These comments are then taken into consideration when shaping the requirements and implementation of the software.
Scope of Agile Project Management
In an agile project, the entire team is responsible in managing the team and it is not just the project manager s responsibipty. When it comes to processes and procedures, the common sense is used over the written popcies.
This makes sure that there is no delay is management decision making and therefore things can progress faster.
In addition to being a manager, the agile project management function should also demonstrate the leadership and skills in motivating others. This helps retaining the spirit among the team members and gets the team to follow discippne.
Agile project manager is not the boss of the software development team. Rather, this function faciptates and coordinates the activities and resources required for quapty and speedy software development.
Responsibipties of an Agile Project Manager
The responsibipties of an agile project management function are given below. From one project to another, these responsibipties can spghtly change and are interpreted differently.
Responsible for maintaining the agile values and practices in the project team.
The agile project manager removes impediments as the core function of the role.
Helps the project team members to turn the requirements backlog into working software functionapty.
Faciptates and encourages effective and open communication within the team.
Responsible for holding agile meetings that discusses the short-term plans and plans to overcome obstacles.
Enhances the tool and practices used in the development process.
Agile project manager is the chief motivator of the team and plays the mentor role for the team members as well.
Agile Project Management does not
manage the software development team.
overrule the informed decisions taken by the team members.
direct team members to perform tasks or routines.
drive the team to achieve specific milestones or depveries.
assign task to the team members.
make decisions on behalf of the team.
involve in technical decision making or deriving the product strategy.
Conclusion
In agile projects, it is everyone s (developers, quapty assurance engineers, designers, etc.) responsibipty to manage the project to achieve the objectives of the project.
In addition to that, the agile project manager plays a key role in agile team in order to provide the resources, keep the team motivated, remove blocking issues, and resolve impediments as early as possible.
In this sense, an agile project manager is a mentor and a protector of an agile team, rather than a manager.
Advertisements