Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
2 views

Agile Software Development_ A gentle introduction_

Agile Software Development emphasizes collaboration, flexibility, and customer involvement in the software development process. It recognizes that software is inherently malleable and that requirements often change, advocating for iterative progress through working software rather than rigid specifications. The document highlights the importance of team dynamics and empowerment over strict adherence to processes for achieving productivity and effective project management.

Uploaded by

zerunx
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
2 views

Agile Software Development_ A gentle introduction_

Agile Software Development emphasizes collaboration, flexibility, and customer involvement in the software development process. It recognizes that software is inherently malleable and that requirements often change, advocating for iterative progress through working software rather than rigid specifications. The document highlights the importance of team dynamics and empowerment over strict adherence to processes for achieving productivity and effective project management.

Uploaded by

zerunx
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

2025/1/21 12:23 Agile Software Development: A gentle introduction.

Agile Software Development: A gentle introduction


Computer science is a young customer, the one who funds the
science. Computer programmers my software development, a valuable and
age were trained by engineers. That essential team member. When the dead
training dictated how we approached line gets close a traditional approach to
software development for an entire reducing scope is to let the developers
generation. But now after decades of decide what will work properly and what
building software to be expensive, won't. Instead let the customer make
unwanted, and unreliable we have come scope decisions a little at a time
to realize software is different. Building throughout the project.
software is more like creating a work of When your customer, or domain
art, it requires creativity in design and expert works directly with the
ample craftsmanship to complete. development team everyone learns
Software remains malleable, often something new about the problem. True
illogical, and incomplete forever. Agile domain expertise and experience is
software development is based on essential to finding a simple, elegant,
fundamental changes to what we correct solution. A document can have Agile also means a fundamental
considered essential to software plenty of information, but real change in how we manage our projects.
development ten years ago. knowledge is hard to put on paper. Left If working software is what you will
The most important thing to know alone programmers must assume they deliver then measure your progress by
about Agile methods or processes is know everything they need. When how much you have right now. We will
that there is no such thing. There are asking questions is difficult or slow the change our management style to be
only Agile teams. The processes we knowledge gap grows. The system will based on getting working software
describe as Agile are environments for get built, but it won't solve the problem done a little at a time. The documents
a team to learn how to be Agile. like one guided by an expert on a daily we used to create as project milestones
We realize the way a team works basis. may still be useful, just not as a
together is far more important than any Perhaps the biggest problem with measure of progress.
process. While a new process can software development is changing Instead of managing our activities
easily improve team productivity by a requirements. Agile processes accept and waiting till the project ends for
fraction, enabling your team to work the reality of change versus the hunt for software, we will manage our
effectively as a cohesive unit can complete, rigid specifications. There are requirements and demonstrate each
improve productivity by several times. domains where requirements can't new version to the customer. It is a
Of course to be eligible for such a big change, but most projects have hard change to make but it opens up
improvement you must be working at a changing requirements. For most new ways to develop software.
fraction of your potential now. projects readily accepting changes can Take a guided tour of Agile
Unfortunately, it isn't that uncommon. actually cost less than ensuring Development by following the
The most brilliant programmers requirements will never change. buttons starting here. Or continue your
alive working competitively in an ego- We can produce working guided tour of Extreme Programming
rich environment can’t get as much software starting with the first week of by following the buttons. Let's look
done as ordinary programmers working development so why not show it to the at how we manage by features next.
cooperatively as a self disciplined and customer? We can learn so much more
self-organizing team. You need a about the project requirements in the
process where team empowerment and context of a working system. The
collaboration thrive to reach your full changes we get this way are usually the
potential. most important to implement.
The second change is making the
Links and Books | Manage by Features | The Paradox of Process | Agile Modeling | Process Proverbs | About the Author
Copyright 2009 Don Wells all rights reserved.

www.agile-process.org 1/1

You might also like