Tom will be presenting the following session
  • Tom Gilb
    Tom Gilb
    Agile Granddaddy
    Gilb International
    schedule 9 months ago
    Sold Out!
    45 Mins

    1. Real Software Engineering, not just about coding, Not ‘CodeFlow’ like some agile methods.

    2. Systems (level) Thinking: even for ‘Programs’ you need to integrate people, data, legal, hardware, cloudware and more.

    3. Stakeholder Engineering: not merely ‘customer and user’: Stakeholder Stories, Stakeholder Xperience (SX not UX)

    4. Simultaneous Multi-Values and Multi-Cost Requirements; as Agile Efficiency Measure, "Agility for Efficiency”.

    5. Multi-Value Flow Optimization, Multi-Constraint Consideration.

    6. Dynamic Design to Efficiency (Value/Cost): The Architect in the Agile Loop (IBM Cleanroom, Evo)

    7. 100X Defect-Prevention from Requirements; using Spec QC + Planguage; at Intel, in practice. (Terzakis)

    8. Dynamic Stepwise Priority Computation, based on Efficiency and Constraints. Using Impact Estimation Tables.

    9. AI, Web 3.0, Solid, Symantic Triples, Ontology& Digitization. = Very High-Tech Agile Future: Bye Bye Yellow Stickies.

    10. Scale-Free Agile methods, as proven big time, at Intel, and other places.

    11. Agile Engineering on a small scale (16 Norway Developers, 4 x 4 Teams, at Confirmit, capture international market with dramatic product quality increases)

    12. "Principles of Agile Engineering” : Logical Common Sense.

    13. μActs: + -> Tailored Practices -> Tailored Methods: BYOM Bring Your Own Method. ‘Essence' and D.A. 

1. What got you started/interested in modern software development methods?

I started them. I started developing systems about 1960 so I made up methods as I went along.

One of the original advocates of Evolutionary Software Development is the internationally known consultant from Norway, Tom Gilb. He served as the technical rapporteur for Symposium IST-034 RSY-OIO, he put on a pro bono course on evolutionary development for the 1ST Panel, and a CD-ROM of material collected by him on evolutionary development was distributed to every member of the 1ST Panel. His website is an important source of tutorial and reference material, as well as examples.

2. What do you think is the biggest challenge faced by the software product engineering community today?

A recognition that they need to use a real systems engineering paradigm, not a coding paradigm. Courage to do the right thing when managers are not good leaders for doing so.

3. What do you think are the most exciting developments in software product engineering today?

My own methods, and next gen AI

The basic idea is to get consultants to focus on Client success in delivering value, and avoid focus on methods and frameworks as such.

SUCCESS Book Folder
(Pages and pdf)

4. Why did you choose the topic(s) you will be speaking about at the conference?

To try to influence people to use engineering methods

5. What are some of the key takeaways from your session(s) at Agile India?

Engineering of systems is necessary for increasing successful projects

6. Any personal remarks/message you want to share with the software community?

Quantify your critical stakeholder objectives, especially technical qualities like security, then Engineer security levels in