How to Spot FAKE AGILE - 7 Strategies

Рет қаралды 614

Күн бұрын

What truly sets agile software development apart from waterfall? It's more than just daily standups and two-week sprints. In this video, David Scott Bernstein reveals seven powerful strategies to transition from waterfall to agile, enhancing your development process and delivering better software.
Join David as he explores:
1. Replacing requirements with stories to improve communication and reduce defects.
2. The critical role of continuous integration in achieving true agility.
3. How test-first development drives better, more focused code.
4. The importance of automating validation for release candidates.
5. The benefits of building smaller features to increase efficiency.
6. Shortening feedback cycles to rapidly detect and fix defects.
7. Adopting other Extreme Programming practices to tackle additional challenges.
Discover how these strategies can transform your software development process and help you fully embrace agility. Don't miss out on these actionable insights that will take your team to the next level.
Software Developer Training and Resources:
- Explore comprehensive courses on software development principles and practices at To Be Agile: ToBeAgile.com
My Developer Essentials Training curriculum shows how to build software using design patterns, refactoring, and test-first development. Contact me (tobeagile.com/contact) if you have a group of ten or more software developers and are interested in a private class. If you or a few of you would like to attend one of my public classes then join my mailing list on my Public Training Schedule (tobeagile.com/training) and Iwill notify you when registration opens for next public class.
- Deepen your understanding with my book, "Beyond Legacy Code: Nine Practices to Extend the Life and Value of Your Software": BeyondLegacyCode.com
For AI Enthusiasts:
- Master prompt engineering with "Prompt Engineering for Everyone: A Comprehensive Guide to Unlock the Potential of ChatGPT and AI Language Models". Get your copy on Amazon: www.amazon.com/dp/B0CFDT76YW
Next Video in the Series:
- Check out my channel, @ThePassionateProgrammer for more videos -
/ @thepassionateprogrammer
Your Thoughts Matter:
- Have questions, suggestions, or ideas? Share your thoughts in the comments below. I'm excited to hear from you!
#ThePassionateProgrammer #DavidScottBernstein #SoftwareDevelopment #AIPromptEngineering

Пікірлер: 5

@fashionrebelution 18 күн бұрын

Great ideas. You really know what you are talking about. I’m super stoked to see how much these ideas can help the industry.

@ThePassionateProgrammer 18 күн бұрын

More to come!

@donstratton6343 7 күн бұрын

Strongly disagree about the user stories approach. User stories generate a solution from the user's perspective, a perspective that may not state the total business response to an event. What if a better business solution would make that user's role obsolete? Business requirements derived from business rules, not wants, drive solution design from a business perspective. You seem to want to discard a waterfall approach based on good practices in the programming phase. The baby is being thrown out with the bath water.

@ThePassionateProgrammer 5 күн бұрын

What are your sources of information about user stories? My friend Ron coined the term. User stories DO NOT have to only come from users. The first part of a story is the role, “As a _____,” That role could be a user, stakeholder, executive, an external system, etc. But it is better to have the focus of a user story be the outcome of applying the business rule rather than the business rule itself. Read Mike Cohn’s book, User Stories Applied if you want to learn what user stories are and how to use them well.

@donstratton6343 5 күн бұрын

@@ThePassionateProgrammer Thank you for replying. The focus is a study of the events that cause the business area to do work. Data arriving at the business area creates a total business response from the perspective of the business. An alternative and more comprehensive approach to user stories is event analysis driving requirements definition that becomes the foundation for conceptual design. My source for user stories was while working in a large corporation in the US in the 1990's witnessing user stories missed only to be demanded as essential later while other stories were included that were really outside the scope of the business area. I saw this happen on three separate projects.