The document provides an introduction to Agile project management. It defines Agile and explains its core principles and practices. Some key points covered include:
- Agile emphasizes face-to-face communication, collaboration between business and developers, and frequent demonstrations of working software.
- The Agile Manifesto, signed in 2001, established core values like responding to change over following a plan and valuing individuals and interactions.
- Agile avoids big upfront design and documentation, favors iterative development, and emphasizes collaboration and empowering motivated teams.
Join BostonPHP and Michael Bourque as he presents the concept of Scrum and shows why so many people are now deploying scrum to their development projects. Michael will take us through the process and talk about how his company, Parametric Technology Inc. (PTC) , is successfully applying Scrum.
Cost of Delay: An Economic Approach to Decision MakingRoger Turnau
Cost of Delay is a lightweight approach to feature and product prioritization that asks a simple question: how much does it cost you not to have something? Reinertsen has said that Cost of Delay is the most important thing to quantify when producing a product. Great, but how do you start? How do you assign a dollar amount to something you have not built yet? How do we make sure that our teams focus on building the most important thing right now? This talk will give you the tools you need to understand Cost of Delay, as well as a set of techniques, from simple proxies to more sophisticated real-dollar analyses to help you understand the impact of delays on your organization.
Getting Started - Introduction to Sprint ReviewsEasy Agile
Overview
- What is a sprint review?
- Benefits of sprint reviews
- Anatomy of a sprint review
- Guidelines for effective sprint review meetings
- conducting sprint reviews using Easy Agile User Story Maps
In this presentation, I talk of Donald Reinstern's original idea of quantifying using Money units per time unit. However, the Agile world has been comprised a bit by using Fibonacci series or a scale of 1 to 10. Are we compromising the original intent of the author?
Do you have Product Owners or work with them? This talk is aimed at agile coaches and scrum masters to help their PO's in areas they are struggling. We will illustrate 2 techniques to help them with prioritisation and capacity planning.
To get exclusive access to a new techniques from us each month, sign up to our newsletter: http://bit.ly/W1dP3o
Introduction to Agile Estimation & PlanningAmaad Qureshi
Presented by Natasha Hill & Amaad Qureshi
In this session, we will be covering the techniques of estimating Epics, Features and User Stories on an Agile project and then of creating iteration and release plans from these artefacts.
Agenda
1. Why traditional estimation approaches fail
2. What makes a good Agile Estimating and Planning approach.
3. Story points vs. Ideal Days
4. Estimating product backlog items with Planning Poker
5. Iteration planning - looking ahead and estimating no more than a few week ahead.
6. Release planning - creating a longer term plan, typically looking ahead, 3-6 months
7. Q&A
The Product Backlog drives the work of Scrum teams, but keeping the backlog fresh and useful is often a continuing challenge. Is your product backlog healthy, and what are some ways to keep it that way that you can use right away?
Being Agile, Doing Agile and Agile in Crisis: We have the Agile Industrial Complex, Dark Agile, Faux/Fake Agile, Zombie Scrum, Flaccid Scrum, CrAgile, FrAgile, WAgile, and more. What do they all mean, and how do we know if we are doing them instead of "Being Agile"
Actionable Agile Metrics for Predictability - Daniel VacantiAgile Montréal
Actionable Agile Metrics for Predictability
“When will it be done?” That's the first question customers ask once work is started. Your predictability is judged by the accuracy of your answer. Think about how many times you’ve been asked that question and how many times you’ve been wrong. That you’ve been wrong more times than right is not necessarily your fault. You have been taught to collect and analyze the wrong metrics. Until now.
About Daniel Vacanti
Daniel Vacanti is a 20+ year software industry veteran who has spent most of his career focusing on Lean and Agile practices. In 2007, he helped to develop the Kanban Method for knowledge work and managed the world’s first project implementation of Kanban that year. He has been conducting Lean-Agile training, coaching, and consulting ever since. In 2011 he founded ActionableAgile (previously Corporate Kanban) which provides industry-leading predictive analytics tools and services organizations that utilize Lean-Agile practices. In 2015 he published his book, “Actionable Agile Metrics for Predictability”, which is the definitive guide to flow-based metrics and analytics. Daniel holds an M.B.A. and regularly teaches a class on lean principles for software management at the University of California Berkeley.
Summary: Update and coordination between the Team members.
Participants: Team is required; Product Owner is optional; ScrumMaster is usually present but ensures
Team holds one.
Duration: Maximum length of 15 minutes.
Once the Sprint has started, the Team engages in another of the key Scrum practices: The Daily
Scrum. This is a short (15 minutes or less) meeting that happens every workday at an appointed time.
Everyone on the Team attends. To keep it brief, it is recommended that everyone remain standing. It is
the Team’s opportunity to synchronize their work and report to each other on obstacles. In the Daily
Scrum, one by one, each member of the Team reports three things to the other members of the Team: (1)
What has been accomplished since the last meeting?; (2) What will be done before the next meeting?;
and (3) What obstacles are in the way?.
Imported from Japan, Kanban is an agile methodology that is gaining a lot of traction. Kanban, or Japanese for signal card, is a process that focuses on transparency and limiting the work in progress. By utilizing Kanban, you can pinpoint the bottlenecks and address them easily. In this session you will learn what Kanban is, how it evolved from its roots in the Toyota Production System (TPS) and lean manufacturing to software development, Kanban’s benefits, and how best to implement a Kanban system. We’ll also discuss when not to use Kanban and how to modify other agile methodologies, such as Scrum, to be used in conjunction with Kanban.
Industries across the globe are burgeoning. Stiff
competition has permeated every stratum among
enterprises. To sustain themselves in such an environment,
companies are seeking new and improved methods by which
they can revamp their business and also their existing
production processes. With the emphasis firmly resting on the requirement for
more robust processes, companies are transforming their
project plans drastically. Now, the buzz and objective is to
move on to a more adaptive process that ushers in change
and provides results. Moreover, businesses need a process
that offers enhanced flexibility which can alter the very
nature of the process itself.
Join BostonPHP and Michael Bourque as he presents the concept of Scrum and shows why so many people are now deploying scrum to their development projects. Michael will take us through the process and talk about how his company, Parametric Technology Inc. (PTC) , is successfully applying Scrum.
Cost of Delay: An Economic Approach to Decision MakingRoger Turnau
Cost of Delay is a lightweight approach to feature and product prioritization that asks a simple question: how much does it cost you not to have something? Reinertsen has said that Cost of Delay is the most important thing to quantify when producing a product. Great, but how do you start? How do you assign a dollar amount to something you have not built yet? How do we make sure that our teams focus on building the most important thing right now? This talk will give you the tools you need to understand Cost of Delay, as well as a set of techniques, from simple proxies to more sophisticated real-dollar analyses to help you understand the impact of delays on your organization.
Getting Started - Introduction to Sprint ReviewsEasy Agile
Overview
- What is a sprint review?
- Benefits of sprint reviews
- Anatomy of a sprint review
- Guidelines for effective sprint review meetings
- conducting sprint reviews using Easy Agile User Story Maps
In this presentation, I talk of Donald Reinstern's original idea of quantifying using Money units per time unit. However, the Agile world has been comprised a bit by using Fibonacci series or a scale of 1 to 10. Are we compromising the original intent of the author?
Do you have Product Owners or work with them? This talk is aimed at agile coaches and scrum masters to help their PO's in areas they are struggling. We will illustrate 2 techniques to help them with prioritisation and capacity planning.
To get exclusive access to a new techniques from us each month, sign up to our newsletter: http://bit.ly/W1dP3o
Introduction to Agile Estimation & PlanningAmaad Qureshi
Presented by Natasha Hill & Amaad Qureshi
In this session, we will be covering the techniques of estimating Epics, Features and User Stories on an Agile project and then of creating iteration and release plans from these artefacts.
Agenda
1. Why traditional estimation approaches fail
2. What makes a good Agile Estimating and Planning approach.
3. Story points vs. Ideal Days
4. Estimating product backlog items with Planning Poker
5. Iteration planning - looking ahead and estimating no more than a few week ahead.
6. Release planning - creating a longer term plan, typically looking ahead, 3-6 months
7. Q&A
The Product Backlog drives the work of Scrum teams, but keeping the backlog fresh and useful is often a continuing challenge. Is your product backlog healthy, and what are some ways to keep it that way that you can use right away?
Being Agile, Doing Agile and Agile in Crisis: We have the Agile Industrial Complex, Dark Agile, Faux/Fake Agile, Zombie Scrum, Flaccid Scrum, CrAgile, FrAgile, WAgile, and more. What do they all mean, and how do we know if we are doing them instead of "Being Agile"
Actionable Agile Metrics for Predictability - Daniel VacantiAgile Montréal
Actionable Agile Metrics for Predictability
“When will it be done?” That's the first question customers ask once work is started. Your predictability is judged by the accuracy of your answer. Think about how many times you’ve been asked that question and how many times you’ve been wrong. That you’ve been wrong more times than right is not necessarily your fault. You have been taught to collect and analyze the wrong metrics. Until now.
About Daniel Vacanti
Daniel Vacanti is a 20+ year software industry veteran who has spent most of his career focusing on Lean and Agile practices. In 2007, he helped to develop the Kanban Method for knowledge work and managed the world’s first project implementation of Kanban that year. He has been conducting Lean-Agile training, coaching, and consulting ever since. In 2011 he founded ActionableAgile (previously Corporate Kanban) which provides industry-leading predictive analytics tools and services organizations that utilize Lean-Agile practices. In 2015 he published his book, “Actionable Agile Metrics for Predictability”, which is the definitive guide to flow-based metrics and analytics. Daniel holds an M.B.A. and regularly teaches a class on lean principles for software management at the University of California Berkeley.
Summary: Update and coordination between the Team members.
Participants: Team is required; Product Owner is optional; ScrumMaster is usually present but ensures
Team holds one.
Duration: Maximum length of 15 minutes.
Once the Sprint has started, the Team engages in another of the key Scrum practices: The Daily
Scrum. This is a short (15 minutes or less) meeting that happens every workday at an appointed time.
Everyone on the Team attends. To keep it brief, it is recommended that everyone remain standing. It is
the Team’s opportunity to synchronize their work and report to each other on obstacles. In the Daily
Scrum, one by one, each member of the Team reports three things to the other members of the Team: (1)
What has been accomplished since the last meeting?; (2) What will be done before the next meeting?;
and (3) What obstacles are in the way?.
Imported from Japan, Kanban is an agile methodology that is gaining a lot of traction. Kanban, or Japanese for signal card, is a process that focuses on transparency and limiting the work in progress. By utilizing Kanban, you can pinpoint the bottlenecks and address them easily. In this session you will learn what Kanban is, how it evolved from its roots in the Toyota Production System (TPS) and lean manufacturing to software development, Kanban’s benefits, and how best to implement a Kanban system. We’ll also discuss when not to use Kanban and how to modify other agile methodologies, such as Scrum, to be used in conjunction with Kanban.
Industries across the globe are burgeoning. Stiff
competition has permeated every stratum among
enterprises. To sustain themselves in such an environment,
companies are seeking new and improved methods by which
they can revamp their business and also their existing
production processes. With the emphasis firmly resting on the requirement for
more robust processes, companies are transforming their
project plans drastically. Now, the buzz and objective is to
move on to a more adaptive process that ushers in change
and provides results. Moreover, businesses need a process
that offers enhanced flexibility which can alter the very
nature of the process itself.
Top 50 Agile Interview Questions and Answers.pdfJazmine Brown
Top 50 Agile Interview Questions and Answers
Many organizations and businesses are taking notice of the agile technique. In today's world, it has become the benchmark for project management and software development. Various firms now use agile methodologies to offer high-value goods to their clients in the lowest amount of time.
In recent years, the agile technique has grown in popularity, and as a result, businesses have adopted it into their organizational structures. As a result, professionals with knowledge of agile are in high demand. As a result, you may have a lucrative career in this field.
These Agile interview questions and answers are great for you if you are planning to attend an agile interview and are preparing for one.
We hope that this post will familiarize you with some of the top agile interview questions that are most commonly raised in the interview. These flexible agile interview questions will improve your chances of passing your forthcoming interview.
50 top agile interview questions along with concrete answers
We have formulated the top agile interview questions and answers based on three different levels of entry into the profession along with scenario-based questions.
Beginner/Entry-Level Agile Interview questions and Answers
1. Explain agile methodology.
Agile methodology is a software development paradigm that emphasizes iterative and incremental development. The agile strategy is based on delivering a product in tiny operational increments or builds. Every program built is a better and more advanced version of the previous one. The development team and stakeholders are constantly collaborating on enhancements and changes in requirements.
Alternatively, we can describe the agile approach as the process of continuously providing functioning software while maintaining regular communication with stakeholders in order to ensure customer satisfaction.
2. How many types of Agile Methodologies are there? Enumerate them.
Agile Methodologies are classified into seven different types. They are:
• Scrum
• Kanban
• Extreme Programming
• Feature-Driven Development (FDD)
• Dynamic Systems Development Method (DSDM)
• Lean
• Crystal
3. What are the merits and demerits of the agile technique?
The following are some of the most noteworthy benefits of the agile methodology:
• Agile software development is one of the quickest and most flexible methodologies available.
• During the development phase, customers might adjust their needs at any time.
• It largely focuses on the software product's regular release. As a result, clients have the opportunity to see the product in its early stages of development.
• Customers have the option of providing comments on any working deliverable they receive.
• Because the development team focuses on creating a product that matches the customer's needs, this strategy ensures customer happiness.
• It focuses mostly on the product's good design.
Agile project management is becoming a key skill within the software industry. As more businesses adopt agile, they are seeking dedicated agile project management methods to help them. Individuals with agile certifications in project management can therefore command a premium in the jobs market. Read on to find out more about agile and project management and professional certification.
Agile is a very popular project management method. It is especially useful in managing rapid deployment of new product features in measured cycles. SharePoint 2013 can be leveraged as a platform for managing Agile
What is scaling and how can it help to improve your organisation? What is the right mix of scaling principles and practices for your culture and teams? I will compare some agile approaches on scaling like Scaled Agile Framework aka SAFe, Large Scale Scrum (LeSS) both based on principles of Lean Product Development and Scaling Agile @ Spotify.
Rich Mironov's keynote for one-day agile workshop. Intro to agile development and agile organizations, tools, impact on whole organization, product management and product planning. Co-sponsored by AccuRev, Coverity, Electric Cloud, Enthiosys, Rally and Agile Journal.
The Agile Method and AGILE ISD; how to use each to improve your training programChristopher King
The term "agile" is being used readily to express the desire organizations have to be responsive and flexible to change in their organization. The Agile development method is designed to quickly and efficiently produce software products. Recently its application has expanded to other areas including training products. AGILE ISD is a new way of thinking about education where performance is the metric that drives the development and delivery decisions in an organization’s training program. It recognizes the long tail of learning and the five moments of learning need. AGILE ISD provides strategies for creating a culture of learning at your organization.
While these two agile methods are for different purposes, they are not mutually exclusive. This session will explain how your organization can use both methods to your advantage and success. We clarify some of the different uses of the term agile within the learning and development community. In this session we will cover:
• Agile (software) movement - its history, its main tenets, different types of agile frameworks and how to incorporated into the ADDIE training methodology
• AGILE ISD – is a methodology developed by Dr. Conrad Gottfredson that aims to supplement ADDIE by expanding its scope to include informal learning design. We cover its history, its main tenants, principles of agile education, and incorporating AGILE ISD into the ADDIE training methodology
• How the two approaches can both be successfully applied in your L&D organization
More organizations are recognizing the many benefits that Agile delivers.
As organizations start embracing the approach, there are gaps in understanding about what it is, what it involves and what value it brings.
What is Agile Development is the first in a series of Agile eBooks from Intelliware Development intended to help eliminate those gaps.
Similar to PMI-ACP Lesson 01 Nugget 1 Introduction to Agile (20)
1. Why are Customers adopting a Serverless-first Strategy?
AXA >> Rearchitecting with Serverless to accelerate innovation
2. Thinking Serverless >> from Business Problem to Serverless Solution ⚡
3. Getting started with Serverless for Developers
The fundamentals of AWS Cloud Security 🛠⛅️🚀Thanh Nguyen
1. Control your Cloud Infrastructure: AWS IAM
✍️ Identities that can make AWS calls
✍️ How to read and write IAM policy
2. Control your Data: AWS KMS
✍️ How AWS KMS integrates with AWS services
✍️ How to authorize access to AWS KMS keys
3. Control your Network: Amazon VPC ⛅️
✍️ How to get least-privilege connectivity
✍️ How to use your network as a security perimeter
https://datalake.aws.job4u.io/en/
You are a Data Analytics Team at Unicorn-Taxi Startup. You’ve been asked to help with the following tasks:
* Create a Dataset for Reporting and Visualization: Cleanse, Transform, Optimize for Reporting Queries
* Help solve a Machine Learning problem: Unicorn-Taxi’s Data Scientists need to understand Passenger tipping behavior
Introduction to Ethereum Blockchain & Smart ContractThanh Nguyen
The Harvard Business Review (HBR) thinks that Blockchain Technology has to power to keep data safe for consumers and businesses alike; because Blockchain provides a secure and immutable ledger, HBR says it represents the key to taking back privacy of data.
“You can keep certified copies of identity documents, biometric test results, health data, or academic and training certificates online, available at all times, yet safe unless you give away your key. At a whole system level, the database is very secure.”
Public Speaking Tips to Help You Be A Strong Leader.pdfPinta Partners
In the realm of effective leadership, a multitude of skills come into play, but one stands out as both crucial and challenging: public speaking.
Public speaking transcends mere eloquence; it serves as the medium through which leaders articulate their vision, inspire action, and foster engagement. For leaders, refining public speaking skills is essential, elevating their ability to influence, persuade, and lead with resolute conviction. Here are some key tips to consider: https://joellandau.com/the-public-speaking-tips-to-help-you-be-a-stronger-leader/
Org Design is a core skill to be mastered by management for any successful org change.
Org Topologies™ in its essence is a two-dimensional space with 16 distinctive boxes - atomic organizational archetypes. That space helps you to plot your current operating model by positioning individuals, departments, and teams on the map. This will give a profound understanding of the performance of your value-creating organizational ecosystem.
Comparing Stability and Sustainability in Agile SystemsRob Healy
Copy of the presentation given at XP2024 based on a research paper.
In this paper we explain wat overwork is and the physical and mental health risks associated with it.
We then explore how overwork relates to system stability and inventory.
Finally there is a call to action for Team Leads / Scrum Masters / Managers to measure and monitor excess work for individual teams.
Employment PracticesRegulation and Multinational CorporationsRoopaTemkar
Employment PracticesRegulation and Multinational Corporations
Strategic decision making within MNCs constrained or determined by the implementation of laws and codes of practice and by pressure from political actors. Managers in MNCs have to make choices that are shaped by gvmt. intervention and the local economy.
The case study discusses the potential of drone delivery and the challenges that need to be addressed before it becomes widespread.
Key takeaways:
Drone delivery is in its early stages: Amazon's trial in the UK demonstrates the potential for faster deliveries, but it's still limited by regulations and technology.
Regulations are a major hurdle: Safety concerns around drone collisions with airplanes and people have led to restrictions on flight height and location.
Other challenges exist: Who will use drone delivery the most? Is it cost-effective compared to traditional delivery trucks?
Discussion questions:
Managerial challenges: Integrating drones requires planning for new infrastructure, training staff, and navigating regulations. There are also marketing and recruitment considerations specific to this technology.
External forces vary by country: Regulations, consumer acceptance, and infrastructure all differ between countries.
Demographics matter: Younger generations might be more receptive to drone delivery, while older populations might have concerns.
Stakeholders for Amazon: Customers, regulators, aviation authorities, and competitors are all stakeholders. Regulators likely hold the greatest influence as they determine the feasibility of drone delivery.
Enriching engagement with ethical review processesstrikingabalance
New ethics review processes at the University of Bath. Presented at the 8th World Conference on Research Integrity by Filipa Vance, Head of Research Governance and Compliance at the University of Bath. June 2024, Athens
Specific ServPoints should be tailored for restaurants in all food service segments. Your ServPoints should be the centerpiece of brand delivery training (guest service) and align with your brand position and marketing initiatives, especially in high-labor-cost conditions.
408-784-7371
Foodservice Consulting + Design
Senior Project and Engineering Leader Jim Smith.pdfJim Smith
I am a Project and Engineering Leader with extensive experience as a Business Operations Leader, Technical Project Manager, Engineering Manager and Operations Experience for Domestic and International companies such as Electrolux, Carrier, and Deutz. I have developed new products using Stage Gate development/MS Project/JIRA, for the pro-duction of Medical Equipment, Large Commercial Refrigeration Systems, Appliances, HVAC, and Diesel engines.
My experience includes:
Managed customized engineered refrigeration system projects with high voltage power panels from quote to ship, coordinating actions between electrical engineering, mechanical design and application engineering, purchasing, production, test, quality assurance and field installation. Managed projects $25k to $1M per project; 4-8 per month. (Hussmann refrigeration)
Successfully developed the $15-20M yearly corporate capital strategy for manufacturing, with the Executive Team and key stakeholders. Created project scope and specifications, business case, ROI, managed project plans with key personnel for nine consumer product manufacturing and distribution sites; to support the company’s strategic sales plan.
Over 15 years of experience managing and developing cost improvement projects with key Stakeholders, site Manufacturing Engineers, Mechanical Engineers, Maintenance, and facility support personnel to optimize pro-duction operations, safety, EHS, and new product development. (BioLab, Deutz, Caire)
Experience working as a Technical Manager developing new products with chemical engineers and packaging engineers to enhance and reduce the cost of retail products. I have led the activities of multiple engineering groups with diverse backgrounds.
Great experience managing the product development of products which utilize complex electrical controls, high voltage power panels, product testing, and commissioning.
Created project scope, business case, ROI for multiple capital projects to support electrotechnical assembly and CPG goods. Identified project cost, risk, success criteria, and performed equipment qualifications. (Carrier, Electrolux, Biolab, Price, Hussmann)
Created detailed projects plans using MS Project, Gant charts in excel, and updated new product development in Jira for stakeholders and project team members including critical path.
Great knowledge of ISO9001, NFPA, OSHA regulations.
User level knowledge of MRP/SAP, MS Project, Powerpoint, Visio, Mastercontrol, JIRA, Power BI and Tableau.
I appreciate your consideration, and look forward to discussing this role with you, and how I can lead your company’s growth and profitability. I can be contacted via LinkedIn via phone or E Mail.
Jim Smith
678-993-7195
jimsmith30024@gmail.com
The Team Member and Guest Experience - Lead and Take Care of your restaurant team. They are the people closest to and delivering Hospitality to your paying Guests!
Make the call, and we can assist you.
408-784-7371
Foodservice Consulting + Design
1. Copyright 2014, Simplilearn, All rights reserved.1
PMI® & ACP are the registered marks of Project Management Institute, Inc. Copyright 2014, Simplilearn, All rights reserved.
Introduction to Agile
PMI®—Agile Certified Practitioner (PMI-ACP)®
2. Copyright 2014, Simplilearn, All rights reserved.2
● Explain Agile development
● Describe the principles of Agile Manifesto
● List the core values and principles of Agile
● Explain what is not Agile
● Describe the benefits of Agile methodologies
After completing
this lesson, you will
be able to:
Objectives
3. Copyright 2014, Simplilearn, All rights reserved.3
Agile is a family of project development processes.
Agile emphasizes:
● face-to-face communication;
● business and developer collaboration;
● working software as the primary demonstration of progress;
● emphasis on effective engineering techniques;
● frequent demonstrations of progress and early return on
investment;
● adaptation to business change; and
● retrospectives and continuous improvement.
What Is Agile
4. Copyright 2014, Simplilearn, All rights reserved.4
Agile evolved in the late 1990s in response to the burdens of heavy documentation and frequent
requirements change. It started as a collection of lightweight and quality driven approaches to
software development. Some of the more prominent techniques included:
How Has Agile Evolved
Merging all developer working copies with a shared mainline several times a day.
Writing tests before writing software. This creates a rich collection of tests.
Test Driven
Development
Continuous
Integration
The process of restructuring existing computer code without changing its
external behavior.
Refactoring
Technique that captures the end user requirement and what a user needs to do
as part of his job function, in one or more sentences in simple language.User Stories
5. Copyright 2014, Simplilearn, All rights reserved.5
Agile Manifesto
The Agile Manifesto was
signed in February 2001 by a
group of 17 leading software
developers.
This is considered the key
reference for all Agile
practices.
6. Copyright 2014, Simplilearn, All rights reserved.6
Principles of Agile Manifesto
Following are the 12 principles given in the Agile Manifesto:
7. Copyright 2014, Simplilearn, All rights reserved.7
With the Agile Manifesto, a framework for approaching agile development was created and this led to
a clearer definition of the term Agile.
Definition of Agile
Agile is an iterative and incremental (evolutionary) approach to project development
which is performed in a highly collaborative manner by self-organizing teams with
"just enough" ceremony that produces high quality software in a cost effective and
timely manner which meets the changing needs of its stakeholders.
- Scott Ambler, www.agilemodeling.com , Managing Agile Projects
8. Copyright 2014, Simplilearn, All rights reserved.8
Over time, Lean and Six Sigma techniques began to infuse themselves into Agile practices.
These include the following:
Agile—Less Engineering, More Enabling
The entire team regularly discussing what worked and what didn’t work in an iteration.
Continuous
Improvement
Extending Agile techniques, particularly ‘Pull’, across each segment of the value chain.
Focus on the
Value Chain
Understanding the business value of work and prioritizing effort around this work.
Business Value
Emphasis
Delivering measurable value early in the project lifecycle.
Incremental
Delivery
9. Copyright 2014, Simplilearn, All rights reserved.9
The PMI-ACP recognizes a number of core Agile principles and practices.
Agile Core Principles and Practices
10. Copyright 2014, Simplilearn, All rights reserved.10
Agile does not involve:
● big design and requirement gathering up-front;
● predictions on project completion;
● ‘death march’ projects where project teams make up the difference for poor estimates with unpaid
overtime;
● use of tools that force behaviors, such as, task management tools;
● top down management/control; and
● ‘heavy’ documentation, particularly Status Reports, Software Architecture Diagrams, Software
Requirements Specifications, Test Plans etc.
What Is Not Agile
11. Copyright 2014, Simplilearn, All rights reserved.11
As Agile has rapidly become one of the more popular and effective techniques to manage projects, it
is important to understand the benefits to its adopters.
● Emphasis on collaboration, team empowerment, and frequent demonstrations of progress
● Lightweight, relies on whiteboards, index cards, and facilitation techniques
● Very appealing to developers with its development focus
● Idea of time-to-market opportunities and driving the features of the development lifecycle
● Agile focus on pull instead of push
● Simple and easy to understand
● Contemporary
Benefits of Agile
12. Copyright 2014, Simplilearn, All rights reserved.12
Struggling with traditional methods, Kiandra, a custom software development and outsourced IT
Services company decided to take up agile transformation. They realized that Agile provides better
outcomes than the traditional software development approaches. The graphic below shows how the
transformation benefitted them as they developed each portal and gained a better understanding of
Agile principles and practices.
Agile—Real Life Example
Portal 1
Delivered all the
features in half the time
and for 10% less than
originally estimated.
Portal 2
Delivered in 30% less time
and 10% less cost than
originally estimated with
half the functionality
deployed early.
Portal 3
Reduced the time taken
for placing a business
order from ten minutes
to three minutes. It was
80% less than what it
had taken to do a similar
project two years
before.
The outcomes of the changes made to the requested features in various web portals are:
14. Copyright 2014, Simplilearn, All rights reserved.
QUIZ
a.
b.
c.
d.
14
What does the Agile Manifesto principle “Build projects around motivated individuals”
mean?1
The best architectures emerge from self-organizing teams
Trust the team to get the job done
Do projects that will ‘excite’ the customers
Only engage in projects that motivate individuals
15. Copyright 2014, Simplilearn, All rights reserved.
QUIZ
a.
b.
c.
d.
15
What does the Agile Manifesto principle “Build projects around motivated individuals”
mean?1
Answer: c.
Explanation: Principle number 5 of Agile Manifesto states, “Build projects around motivated
individuals. Give them the environment and support they need and trust them to get the
job done.”
The best architectures emerge from self-organizing teams
Trust the team to get the job done
Do projects that will ‘excite’ the customers
Only engage in projects that motivate individuals
16. Copyright 2014, Simplilearn, All rights reserved.
QUIZ
a.
b.
c.
d.
16
Which of the following is not seen as a benefit of Agile?
2
Accurate predictions of project completion
Lightweight, relies on whiteboards, index cards, and facilitation techniques
Implicitly focuses on ‘pull vs. push’
Emphasis on collaboration, team empowerment, frequent demonstrations of progress
17. Copyright 2014, Simplilearn, All rights reserved.
QUIZ
a.
b.
c.
d.
17
Which of the following is not seen as a benefit of Agile?
2
Answer: b.
Explanation: Agile does not emphasize accurate project completion as a benefit of its
practices.
Accurate predictions of project completion
Lightweight, relies on whiteboards, index cards, and facilitation techniques
Implicitly focuses on ‘pull vs. push’
Emphasis on collaboration, team empowerment, frequent demonstrations of progress
18. Copyright 2014, Simplilearn, All rights reserved.
QUIZ
a.
b.
c.
d.
18
3
The best designs emerge from code overtime.
Agile does not recommend design as it constrains development velocity.
Designing up-front wastes time that can be better spent on other activities.
Too much emphasis on design limits the amount of requirements gathering.
Why doesn’t Agile recommend Big Design up-front?
19. Copyright 2014, Simplilearn, All rights reserved.
QUIZ
a.
b.
c.
d.
19
Why doesn’t Agile recommend Big Design up-front?
3
Answer: b.
Explanation: Agile does not emphasize trying to design a system in advance of developing it.
Instead, design should evolve and adapt with development and changing requirements.
The best designs emerge from code overtime.
Agile does not recommend design as it constrains development velocity.
Designing up-front wastes time that can be better spent on other activities.
Too much emphasis on design limits the amount of requirements gathering.
20. Copyright 2014, Simplilearn, All rights reserved.
QUIZ
a.
b.
c.
d.
20
4
Why is Continuous Integration seen as valuable?
Integration is hard and often delayed just before the final build; if code is continuously
compiled and checked, conflicts can be identified when they are easy to manage.
It is part of the technique called Kaizen that emphasizes continuous improvement.
It ensures that Scrum of Scrum projects can deliver a potentially implementable
shipment of software.
By using a continuous integration approach, a project can offload many core
development processes to an automated server.
21. Copyright 2014, Simplilearn, All rights reserved.
QUIZ
a.
b.
c.
d.
21
Why is Continuous Integration seen as valuable?
4
Answer: a.
Explanation: One of the learnings from the Chrysler project, where Kent Beck developed XP,
was that code integration was a significant contributor to project delays and defects. He
decided to focus on integrating continuously to identify defects as early as possible.
It is part of the technique called Kaizen that emphasizes continuous improvement.
It ensures that Scrum of Scrum projects can deliver a potentially implementable
shipment of software.
By using a continuous integration approach, a project can offload many core
development processes to an automated server.
Integration is hard and often delayed just before the final build; if code is continuously
compiled and checked, conflicts can be identified when they are easy to manage.
22. Copyright 2014, Simplilearn, All rights reserved.
QUIZ
a.
b.
c.
d.
22
Which of the following Agile Manifesto values is incorrect?
5
Responding to plans over reacting to change
Individuals and interactions over processes and tools
Customer collaboration over contract negotiation
Working software over comprehensive documentation
23. Copyright 2014, Simplilearn, All rights reserved.
QUIZ
a.
b.
c.
d.
23
Which of the following Agile Manifesto values is incorrect?
5
Answer: b.
Explanation: The correct value is “Responding to change over following a plan.”
Responding to plans over reacting to change
Individuals and interactions over processes and tools
Customer collaboration over contract negotiation
Working software over comprehensive documentation
24. Copyright 2014, Simplilearn, All rights reserved.24
● Agile techniques emerged from software engineering approaches to deal
with changing requirements and to improve quality.
● The Agile Manifesto was signed in 2001 that captured the values and
principles of the agile movement.
● Agile Manifesto highlights 12 principles.
● As a lightweight project management approach, Agile avoids big design,
heavy documentation, and top-down management or control.
● Agile emphasizes collaboration, team empowerment, and frequent
demonstrations of progress by focusing on ‘pull vs. push’.
Summary
Here is a quick
recap of what was
covered in this
lesson:
25. Copyright 2014, Simplilearn, All rights reserved.25
Copyright 2014, Simplilearn, All rights reserved.PMI® & ACP are the registered marks of Project Management Institute, Inc.
THANK YOU