استبيان حول مُدرب HRDF ماليزيا

Agile Project Management

• Agile Project Management is a practical approach to managing projects.
• It emphasizes flexibility, lightweight methods, and a team-oriented approach to software development.
• It was officially introduced in 2001.

Agile Project Management Practical Approach

• 17 software developers met in February 2001 to discuss lightweight development methods.
• They created the Agile Manifesto.
• The Agile Manifesto defines the approach now known as agile software development.

Agile Manifesto

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
• Although the items on the right are valuable, the items on the left are more valuable.

Agile vs. Waterfall

• Waterfall: Follow a linear, sequential process. Changes are costly and difficult. Success is measured at the end of the project.
• Agile: Iterative and incremental. Changes are incorporated easily. Success is measured through regular feedback and deliverables.

Agile vs. Waterfall Comparison Chart

• Agile: Changes are welcome even in the late stages.
• Waterfall: Changes are costly and difficult, especially in the late stages.

Standish Group IT Project Success Rates

• Success rates for IT projects fluctuate over time, but they are often lower than desired.

Agile Methodologies

• XP, DSDM, Scrum, Agile Modeling, Agile Data Method, Essential Unified Process, Open UP, Lean software Development, Crystal Methods are Agile frameworks and processes based on Agile Manifesto principles.

Scrum

• Scrum is one of the most popular Agile methodologies used in software and product development.
• It breaks down a product into Sprints (small increments of work).
• Sprints typically take 2–8 weeks.
• The work is done iteratively in each sprint with continuous adjustment and frequent feedback.

Scrum Roles

• Product Owner (PO): Delivers information for the project and interacts with the customer.
• Development Team (DT): The team responsible for creating the product.
• Scrum Master (SM): Facilitates the Scrum process, removes impediments, and ensures the team is effective.

Product Backlog

• The Product Backlog lists all the desired features and capabilities of the product.
• Items are ordered based on value, cost, and time criticality.

Traits of an Effective Scrum Master

• Facilitates Scrum events (like Sprint Retrospectives).
• Helps the team remove obstacles.
• Possesses excellent organizational skills, supporting leadership, and focus on the team's and others' needs.
• Excellent communication, particularly with stakeholders.

Traits of an Effective Product Owner

• Ensures the team builds the right product.
• Helps the team understand the overall mission and goals.
• Acts as the customer's voice, representing customer needs within the team.
• Owns the Product Backlog.

Development Team Traits

• Cross-functional (members possessing diverse skills)
• Self-organizing
• Customer-oriented
• Operates as a team, supporting each other in achieving the team's goals.
• The optimal team size is 3–9 members.

Business Collaboration

• Continuously gathering feedback from customers and stakeholders is key to success.
• Frequent, iterative meetings with stakeholders ensure everyone is on the same page.
• Changes in requirements are welcomed and integrated.

Key Concepts

• Agile principles focus on delivering value to the customer.
• Continuous improvement is crucial.
• Flexibility and adaptability are essential for dealing with evolving needs.
• Collaboration and communication are paramount between stakeholders and the development team.
• Optimizing delivery of product/service through prioritizing the product backlog to meet customer demands.