Metadata
- Author: Cliff Berg
- Full Title:: Agile vs. Agile 2: What’s the Difference?
- Category:: 🗞️Articles
- Document Tags:: Data culture, Engineering Management,
- URL:: https://www.techradar.com/news/agile-vs-agile-2-whats-the-difference
- Finished date:: 2024-02-12
Highlights
Agile was in many ways an overreaction (View Highlight)
I should point out that an experienced person will read the Manifesto differently from someone less experienced. For example, an experienced person will read the phrase “self-organizing team” and assume that - of course - some oversight is needed (View Highlight)
There are many other problems with Agile besides scaling. One is that it fails to address data (View Highlight)
Agile 2 covers many other things as well. It addresses data from three perspectives. One is that data is a strategic asset, and must be managed so that one can later correlate it and derive insights. This is a response to the observation that development teams today often fail to catalog the data that they write to NoSQL databases and that gets broadcast to data lakes, resulting in a heap of historical data that is useless for or machine learning analysis, or training (View Highlight)
Another perspective on data is that an organization’s data model needs to be understood by development teams. Too often teams are expected to start coding as soon as an initiative begins, but they do not understand the operational data stores or how data relates. (View Highlight)