The document discusses agile software development principles and practices. It introduces agile concepts like Scrum, XP, Lean, and TDD. It then shares the Agile Manifesto values of individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. The rest of the document outlines agile principles like welcoming changing requirements, delivering working software frequently, having business and developers work together daily, and continuously improving.

1. Antonio RADESCA http://dotnetslackers.com/Community/blogs/antrad /

2. How many peoples do really know agile philosophy? Scrum,XP (not Windows :D),Lean,TDD…do you know something about? How many peoples were really interested? We will see...:D

3. GO!!!

4. www.agilemanifesto.org Kent Beck Mike Beedle Arie van Bennekum Alistair Cockburn Ward Cunningham Martin Fowler James Grenning Jim Highsmith Andrew Hunt Ron Jeffries Jon Kern Brian Marick Robert C. Martin Steve Mellor Ken Schwaber Jeff Sutherland Dave Thomas

5. PRINCIPLE Word that indicates a foundation or a basic element of philosophical or ideological theory. It is transferred on the object of the same theory and in such case it regards the substance (or essence) of it. DOGMA Generally used in order to define the opinions formulated from the philosophers like base to their doctrines, that fidels can’t doubt

6. We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.

7. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

8. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

9. ?

10. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

11. So what is ALT .NET? And how does it differ from the .NET that we already know and love? What are these values that many of us think are missing? What are these alternative tools, techniques, and practices that ALT .NET'ers are espousing? http://msdn.microsoft.com/en-us/magazine/cc337902.aspx

12. You’re the type of developer who uses what works while keeping an eye out for a better way. You reach outside the mainstream to adopt the best of any community: Open Source, Agile, Java, Ruby, etc. You’re not content with the status quo. Things can always be better expressed, more elegant and simple, more mutable, higher quality, etc. You know tools are great, but they only take you so far. It’s the principles and knowledge that really matter. The best tools are those that embed the knowledge and encourage the principles (e.g. Resharper.) ‏

13. Agile DDD TDD e BDD CI Refactoring Patterns (MVC) ‏ IOC ORM Because we want to develop better software and to be more ready to change!

14. Entity Framework (ORM) ‏ ASP.NET MVC Enterprise Library Unity Application Block,etc (IOC) ‏ MbUnit,NUnit integration in VS JQuery TFS Templates for Agile

15. DDD (Domain Driven Design) ‏ TDD and BDD CI (Continuous Integration) ‏ IOC e AOP Process practices in an Agile environment (SCRUM,XP e MSSF For Agile) ‏