Stakeholder Value Requirements: to deliver the Agile Value Delivery Cycle and to give much clearer requirements for any project
Our free practical tools can be used on a daily basis when planning and discussing IT projects by all levels of experts, managers, business analysts, architects and system or software engineers.
Speaker: Tom Gilb Hon FBCS
17.00pm Finish (approx)
Our risk management methods consist of a large number of free practical tools, which can be added to your current methods incrementally.
- Stakeholder analysis and specification
- Requirement classes (like function, value, performance, quality, constraint)
- How to quantify absolutely all value and quality requirements
- How to structure requirements to cope with complexity of different people, tasks, locations, and other parameters.
- Decomposition of requirements. The key to agile value delivery.
- 'Background' requirement specifications, to aid risk management, quality control, and prioritization.
- There is an opportunity to study deeply, with the most advanced methods, for Agile IT Project Requirement and Design Specification, Analysis, and Quality Control.
- This is suitable for getting substantial powerful knowledge to act as a Scrum Product Owner, or as a Business Analyst.
The skills apply to any kind of system development: IT systems, Organisational Improvement, Product Development, Systems Engineering, Startups.
The skill profile is sharply different from conventional training, which are based on 'delivering working programs', and on 'functional / use case / user story' level-of-thinking.
Our focus is on the most critical aspects of projects, which at the top level, are about; delivering various values (save money, reduce technical debt, become more flexible for changes), including various qualities (like security, privacy, usability), within constrained or minimised resources (time, money, people, initial and recurrent life cycle costs).
In short our focus is on managing and delivering critical stakeholder values profitably, cost-effectively. This includes the idea of projects that never fail, and always succeed, in early continuous delivery, of a prioritised value stream.
The principles are based on agile ('as it really should be, but is probably not, at your site, yet'), lean (early, problem prevention, early problem correction), and 'Scale free' (the methods work at any scale from tiny to huge).
Teaching Method: Workshop Based.
Theory base: Books 'Competitive Engineering', and 'Value Planning', + extensive specialist papers in a free digital library.
Workshop: Primarily learning by doing. In small teams usually working on a class-chosen problem (fun, interesting, current) as 'one class' working on a project together. Exceptionally, a team can work on their own 'other problem' in parallel.
Tool: we will make use of a PC tool (needsandmeans.com) in the class, but the methods taught are tool independent, and word processors, slide software, and spreadsheets can always be used instead. The tool contains very good teaching guidance to learn by doing. It is based on our books (CE, VP).
Tom Gilb joined IBM in 1958. He has been an international consultant and teacher for 55 years. Written 10 published books. Competitive Engineering (2005), and Value Planning (2016). Tom has developed advanced methods for developing systems of any kind, with emphasis on IT systems and High Quality systems.
He is Honorary Fellow of BCS.
Tom Gilb and his partner Kai Gilb have, together with many professional friends and clients, personally developed the Agile ‘Engineering’ methods they teach. The methods have been developed over five decades of practice all over the world in both small companies and projects, as well as in the largest companies and projects. Their website www.Gilb.com/ offers free papers, slides, books, videos, and cases about Agile and many other subjects.
There are many organisations, and individuals, who use some or all of their methods. IBM and HP were two early corporate-wide adopters (1980, 1988). Recently (2016) over 20,000 engineers at Intel have voluntarily adopted the Planguage requirements specification methods; in addition to practicing to a lesser extent Evo, Spec QC and other Gilb methods.
Many other multinationals are in various phases of adopting and practicing the Gilb methods. Many smaller companies also use the methods.
Tom’s methods are 100% risk conscious and devoted to reducing the risks of failure and partial failure, by attention to the details and to the big picture.
Please bring, if possible, a laptop or tablet etc so you can access fully the presentation and other documentation.
THIS EVENT IS BROUGHT TO YOU BY: BCS Quality Specialist Group. To find out more, click here: https://www.bcs.org/category/10130