|
Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise (Agile Software Development Series) by Dean Leffingwell
Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise (Agile Software Development Series) Dean Leffingwell ebook
Format: pdf
Publisher: Addison-Wesley Professional
Page: 559
ISBN: 0321635841, 9780321635846
Lear how to develop a strong and supportive Scaling Software Agility: Best Practices for Large Enterprises (Agile Software Development Series) - (Dean Leffingwell) - Learn how to apply agile methods to enterprise-class development. With agile adoption throughout the industry, it turns out that most of the work tactics of the inglorious past, such as top-to-bottom planning, tracking, big up-front requirements and design, are no longer competitive. Years of software projects and interactive agency-driven initiatives have built strong waterfall muscle memory. Disciplined Agile Delivery addresses agile practices across the entire lifecycle, from requirements, architecture, and development to delivery and governance. Guidance on becoming an Agile technical communicator, while waiting for the rest of the team to adopt and practice the Agile development methodology. I personally know such people – they embrace Lean thinking, paradigms of agile software engineering, and lead teams and programs to better alignment with business needs, a faster flow, and eventually assist the organization in its agile transformation at scale. Agile Project Management: How to Succeed in the Face of Changing Project Requirements - (Gary Chin) - Learn practical strategies for taking charge of crucial but unpredictable projects. In the market there are many more books on Agile Development. What Agile Software Development Learned From Deming by Daryl Kulak - In the last few years software development teams have begun using a philosophy called “Agile”, achieving better results by reducing reliance on documents, having more effective Users (and business managers) are much more effective at giving comments based on working software, even with limitations, than just abstractly creating requirements for a huge number of features in advance. But which ones are really the best of the best?