Review the discussion principles below of the “Manifesto for Agile Software Deve

Question

Review the discussion principles below of the “Manifesto for Agile Software Development” Which of the 12 principles would work well for a two-month project that will build an information site for a small real estate firm? The Agile Alliance (1) defines 12 principles those who want to achieve agility: 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage. 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4. Business people and developers must work together daily throughout the project. 5. Build projects around motivated individuals. Given them the environment and support they need, and trust them to get the job done. 6. The most efficient and effective method of covering information to and within a development team is face-to-face conversion. 7. Working software is the primary measure of progress. 8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9.Continuous attention to technical excellence and good design enhances agility. 10. Simplicity- the art of maximizing the amount of work not done –is essential. 11. The best architectures, requirements, and designs emerge from self-organizing teams. 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Explanation / Answer

12 principles those who want to achieve agility

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

It should be guarded in a secure environment so that no external influences are able to grab its attention.

Changing requirements, even late in development

Do not take any requirement granted as reality is not a static system. People, markets, demands, all things in general are in a constant flow and change.

Deliver working software frequently,

Something finished that is worth being given to the users with early and often so the customer is able to react and decide quickly

Business people and developers must work together

The people with a vast knowledge of the product's target markets, its users and customers, and its needed features. The "product developers" not solely coding software developers. This includes also testers, technical writers, interface designers, business analysts, work on their own and pass over their finished results to the next expert in a process chain.

Build projects around motivated individuals

Search and hire Drive-Driven Personalities who love their job and are passionate about what they're doing.

The most efficient and effective method of conveying information"

to make information available in a passive way by expect active communication from the outside of your team but also foster active communication with your own team members via phone, video, or in the best case in front of a white board from person to person.

Working software

            The only thing that counts is completed and releasable features are important.

Sustainable development

            It's a cross-functional approach involved in the product creation chain. Especially at the end of a project all people should keep calm and just "flow" with that constant pace.

Continuous attention

            Keep your concentration high, stay focused on the things you're working on. Follow a professional honor and build your software product in a way you could be proud of in every detail.

Simplicity

            Think about methods, classes, and your software design in general - you will find various things to be skipped as they do not contribute to your sprint goal or acceptance tests.

The best architectures, requirements, and designs

            The teams have all the necessary roles and skills to create the wanted product, they are able to decide and organize by themselves.

At regular intervals

            if a worst-case "post mortem analysis" could bring up severe issues and action items for the next project, we can't change what already happened. Therefore we have to take a look at our current behaviour in an iterative way.

Related Questions

Navigate

• Browse (All)
• Browse R
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.