-----------------------------------------------------------------------------------

--------------------------------------------------------------
12 Agile Principles
-----------------------------------------------------------------------------------
--------------------------------------------------------------

Agile Principle #1:

Early value Delievery as a Top Priority for the Product Developement
Team by Delievering Increments of the Product Continuosly.
For Example:
If you are building a 'Patient Management System' for a Hospital,

you may first Deliever a Working Software that Captures the

Patient Information,
while you continue to work on Developing other Features like
Capturing the Diagnostic Reports, Doctor's Notes,...

Agile Principle #2:

Welcome Changing Requirements, Even Late in Developement. Agile
Processes Harness Change for the Customer's Competitive Advantage..
Agile Principle #2 talks about Using the Iterative Delievery to
Competitive Advantage by Building a Product that's Current with the Market Needs..
For Example:
In the 'Patient Management System' example, let's say you
delievered the Doctor's Notes feature.
When Doctors see the Demo, they say they don't have Time to enter
the Notes in the system.
So they Request for Voice Notes to Alexa and the Prescription
Scanner.
What should be Done?
- Don't accommodate changes coming late into the game
- Prioritize Features and accommodate them for Upcoming Sprints
Since not doing them make your Product useless for Doctors.

Agile Principle #3:

-----------------------------------------------------------------------------------
--------------------------------------------------------------
4 Agile Values
-----------------------------------------------------------------------------------
--------------------------------------------------------------

Agile Value #1: Processes are Important, but they should Evolve with
Experience to Help People Work Better Together.
We Need Processes to Streamline the Way We Interect & Work Together, Be
it as a Team, Or a Customer & a Service Provider.
Individeuals & Interections Over Processes & Tools...

Agile Value #2: Working Software Over Comprehensive Documentation..

Why do We Need Documents that we Create during Product Developement
like Requirement Specification (PRD), Design Document (DLD)?
- For Future Reference
- To Prove to the Customer that this is What They Said
 - Shared Understanding ***This is Main Purpose

Agile Value #3: Customer Collaboration Over Contract Negotiation

Essence of this Value:
We build a Product to Solve Customer Problems. A Product that doesn't
help Customers get some Job done is useless.
Collaborating with Customes to understand what Adds Value to them while
building Products ,helps you Build a Product that You CAN Actually Sell and
Maximize your ROI.

Agile Value #4: Responding to Change Over Following a Plan

The Goal is Important than following a Specific Plan.
Plan is required but we need to Continuosly Evolve our Plan to Achieve
the Goal.

Question 1: As per Agile Manifesto, Architecture is not important, but the

functionality is.
TRUE --> FALSE
Well, that's a misconception.
The agile manifesto suggests focussing on building the working product in
increments.
So there is no working product without architecture.
Thus as the requirements emerge, the architecture also emerges.

Question 2: Timeboxing is one of the ways to maintain sustainable pace suggested by

Agile Principles.
TRUE
Yes, you can use either timeboxing or work boxing (limit WIP) to have a
sustainable pace.

Question 3: Agile Manifesto suggests building everything that the customer wants.
FALSE
That's right! And that was the last question, good job.

Question 4: Agile Manifesto suggests not to document anything but write code.
FALSE
You know your stuff.

Question 5: Regular and frequent feedback is essential to address customer

collaboration suggested by Agile Manifesto.
TRUE
That's right!

Question 6: When Agile Manifesto suggests “Responding to Change,” it means

releasing products sooner and often to test assumptions.
FALSE --> TRUE
Sorry, you need to understand the Agile Manifesto better. Agility is the
ability to evolve products quickly and continuously to fulfill customer needs.

Question 7: According to Agile Manifesto, Control and Management is important.

TRUE --> FALSE
No, collaboration and self-organization are more critical for agility than
control and management.

Question 8: Agile Manifesto suggests having fewer processes and using no tools.
FALSE -- > TRUE
That's a misconception.
 The processes are required for streamlining the way the teams work to deliver
a valuable outcome.
If the processes hinder the interaction, then it's essential to change your
processes to improve interaction among the team.

Question 9: Agile teams place value in Planning but value responding to change even
more.
TRUE
Yup! Continuous planning is more important than the plan itself.

Question 10: Agile Manifesto suggests defining and implementing the architecture in
the first few iterations to enable teams to deliver working software in subsequent
iterations.
TRUE --> FALSE
Absolutely Not!
Agile Manifesto calls for building a working product to fetch frequent
customer feedback.