Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Scope master introduction presentation feb 2020 w vid
Ähnlich wie Scope master introduction presentation feb 2020 w vid (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Scope master introduction presentation feb 2020 w vid
- 1. Automated analysis of software requirements Solving the problem of poor software requirements – and more Briefing February 2020
- 2. Requirements Quality Really Matters “Entering a sprint with poor requirements may be agile, but it’s certainly not lean” Dr. Simon Wright Based on analysis of over 70,000 user stories by ScopeMaster
- 3. ScopeMaster Company Founder Colin Hammond M.Eng MBCS CFPS colin.hammond@scopemaster.com. Tool ScopeMaster is a unique analyser of software requirements, delivers 50x ROI Team Has over 150 years of IT experience Company ScopeMaster Ltd, est 2018 in the UK. The Goal “Far too much time and effort is wasted on failed or delayed software work. Let’s do better.”
- 4. Requirements Quality Really Matters Mistakes are amplified 1 user story word 125 code ”words” Based on analysis of over 70,000 user stories by ScopeMaster
- 5. Requirements 16.9% Code 26.8% Design Security Documents Bad fixes 1,000 FP Application Source: Capers Jones Applied Software Measurement, third edition Most Activity Unit testing Systems testing Functional testing End to end testing Acceptance testing Root Cause of Defects Found in Production Helps Targets
- 6. Find and fix a requirements problems 2- 5 man hours < 15 minutes to find & fix a requirements problem User Story Refinement Meeting 8 - 20X faster
- 7. 10 Quality Attributes for Better User Stories Unambiguous / clear Measurable / Functional Concise User oriented Testable Consistent Whole and complete Unique Design Free Traceable to business value 9/10 Automated With ScopeMaster
- 8. 1 person No training 90 Stories 2 days 150 defects found & fixed before coding even started! Case Study - Gaming Application Value $35k - $100k, in 2 days https://www.scopemaster.com/case-study/scopemaster-gaming-application/
- 9. Acceptance/Test Criteria … I can click pencil to enter my zip code and full home address Back Given , when & then Functional Aspect of User Stories Requirements in Agile “User Stories” are the catalyst of the conversation. Add Delivery Details As a … I want … So that … Site visitor Add my delivery addresss I can receive my goods SP Who & what Why
- 10. Intelligent Analysis 2. Detects independent steps 1. The tool analyses this 5. Estimates size in COSMIC FP 4. Determines data movements 3. Detects Objects & intent
- 11. Three valuable deliverables Interprets Checks Suggests Finds problems Helps Fix before coding Better specs. Detects functions Reliable estimates De-risk projects Fewer surprises Kickstart testing Save time Requires no set up, just import your requirements and press analyse https://www.scopemaster.com/ 1. 2. 3.
- 12. Analysing a user story Press Play
- 13. Analysing and cross correlating stories - Screenshow Press Play
- 14. Finds and helps Fix Problems - FAST! Press Play
- 15. Detects security risks in requirements Easy to use, fast to learn Portfolio sizing and quality score Requirement level guidance and scoreJust import and press the button
- 16. Testimonials “…it would have saved 3 – 6 months in the requirement’s gathering process” Mike Sanders, Agile PM “..to me it’s a no brainer…” Mike Sanders, Agile PM …this is mindblowing! Lead tester at Bluefruit “……it’s the only static analysis tool for requirements that I have ever seen” Capers Jones Author of 17 software books “…Its amazing….” Prof Alain Abran Head of Computer Science ….doesn’t just help find the requirements defects but helps educate authors to prevent them in future!” Lonnie Franks, Software Guru “Using ScopeMaster, not only I did I find and fix 150 defects in 2 days, it was actually fun to use!” Lonnie Franks, software guru “…I love this tool!” COO/CFO at Borngroup …entering a sprint with poor stories may be agile but its not lean and ScopeMaster is ideal… Dr Simon Wright …it’s a great tool that really uses AI for better project managment! P. Boudreau, Author Speaker on PM …A fantastic solution for automating requirements checks… D. Copesake, Global head of testing B fin Services
- 17. Fits with existing development tools/procedures Refine & size1. Code and Test2. Synchronise Synchronise Any other tools
- 18. Automated Analysis Coding & Testing Software Tools that help you write better software Collaboration
- 19. Valuable x 3 1. Manual Work Automated 20x productivity - finding defects 10x productivity - size estimation 2. Additional Value Knowing the size (better decisions) Risk reduction and cost avoided Overall 10 – 30% cost reduction , ROI of 10x - 50x + 3. Risk Reduction Avoid defect work
- 20. 17 High value, use cases Improving the certainty of software work. ScopeMaster Use Cases Recover failing projects Project Risk reduction Early Estimation Project Assurance Prevent project disasters Early requirements QA Project Oversight Other Better Documentation PMO Improvement Benchmarking Productivity Project Delivery Better, valid metrics Vendor Management Education: Write better user stories Legacy systems lifecycle analysis CIO portfolio assessments Metrics Implementation M&A valuations Functional Test Creation
- 21. $ Time Develop $ Profit from being first to market Breakeven point Early to Market with Strategic IT innovation
- 22. $ Time Impact of delay is compound Develop Market opportunity missed by being late Breakeven point Delayed
- 23. $ Time Impact of delay is compound Develop Market opportunity missed by being late Breakeven point Delayed $
- 24. About Functional Size Valid Standard Non-gameable Suitable for agile Suitable for contracts Ideal for creating estimates Manage: Scope, Resources, Schedule and Quality. Average value of knowing size: 10-40% of total budget.
- 25. NEW. Detects security risks in requirements Checking for Security Risks
- 26. What if you don’t find those defects until coding has begun? 7x - 100x Saving
- 27. • Better Estimates • Faster Delivery • Reduce Re-work • Better Quality • Fewer Bugs • Reduced Project Risk • Lower Cost • Better project resource allocation • Reliable schedule adherence Some of the Benefits of ScopeMaster
- 28. Non Functional Requirements Security Many are functional. Others are config only. Data governance Performance Need specific criteria, consider using Planguage Usability Measurable. UI implementation Maintainability Coding, architecture, patterns and documentation Scalability, Fault Tolerance & Recoverability Architecture, config and data governance Unmanaged NFRs can lead to severe project delays. They can often be managed as risks and dependencies. Measurable but not sizeable : sizing NFRs is not viable but you should aim to quantify the requirement specifics.
- 29. How ScopeMaster helps reduce Architecture Risk Coupling ScopeMaster highlights data coupling between requirements Cohesion ScopeMaster highlights data and requirement relationships Missing, duplicates identification exposes cohesion Functional size is also a good indication of cohesion Complexity ScopeMaster exposing size (an indicator of complexity) Ambiguity exposure leads to lower complexity Architecture attributes that reduce risk:
- 31. Pre-requisites Requirements are written in text in English, French, Spanish Portuguese, Italian or German. Users can become proficient in less than a day. Integrates with existing tools directly or via REST API. Benefits Better requirements, less rework, more stable scope, better planning, shorter timelines, less waste. Overall R.O.I. from 100x achievable in days. Evidence $100k value (150 defects found & fixed) in 2 days. £5m of savings identified in 5 days of consultancy. $40k of potential savings in less than 1 hour. $200k of work won on the basis of automated analysis. Costs Consumption based pricing, from $1.3 per user story. Company ScopeMaster Ltd, a private company created in 2018, UK. ScopeMaster - Overview Problem Poor software requirements work delays projects. The Solution A small team of highly experienced software experts have created ScopeMaster a tool that analyses the text of software requirements. Product ScopeMaster is an online tool (B2B SaaS) used by requirements authors for QA and estimation before coding starts. Applicability Private or public organisations commissioning enterprise software, embedded systems, system software, integration projects, agile or non-agile. Differentiation It is the first and only tool on the market that can analyse requirements for quality, estimation and functional test generation.
- 32. COSMIC Function Points – The best way to measure software work Entry Other interfacing App(s) or devices EXit Application being sized EXit Human Users Persistant storage Read Write Entry ∑𝐸, 𝑋, 𝑅, 𝑊 = 𝐶𝐹𝑃 Appropriate & Valid Consistent Mature and stable Language independent Methodology independent Technology Independent Suitable for all S/W Open source / free ISO Standard
- 33. Sizing software Functional Size Metrics on Software Projects IFPUG FP COSMIC Function Points Very Flawed Not Valid Inconsistent Easy to game Good ISO Standard Consistent User stories insufficient Not ideal for embedded SLOC RICEFW Agile Story Points Flawed Not Valid Inconsistent Easy to game Best ISO Standard Incomplete OK Principle-based Automated US. GAO Recommended
- 34. Story points vs actual effort R2 = 0.33 CFP vs actual effort R2 = 0.97 C. Commeyne, A. Abran, R. Djouab. “Effort Estimation with Story Points and COSMIC Function Points - An Industry Case Study”, Software Measurement News, Vol 21, No. 1, 2016 * Conclusion: CFP is a better predictor of effort than story points. Case study to compare SP vs CFP
- 35. Common PMO Challenges Can we measure the quality of requirements? We commonly see projects seeking more time and budget could this be avoided? We think we are paying too much for development? Our estimates are unreliable? Bug fixing commonly delay our projects? Do we get good value from our development partners?
- 36. Requirements Defects Manual Requirements inspection ScopeMaster Saving Find 1.5 - 5 hours < 5 seconds Fix 0.5 - 1 hours 2 -15 minutes Total 2 - 6 hours 2 - 10 minutes 2+ hours Typical Cost Of effort to find and fix $250 (avg) $20 Effort to Find and Fix Requirements “Defects” 10x Saving
Hinweis der Redaktion
- People write poor requirements We have analysed 50,000 user stories Average size is 6 CFP Average LOC per CFP is 50 Average words per requirements is 10 Average words per LOC is 5 10 / 50x5x5 = 1:125 Opinions: Requirements = User stories Requirements != User stories As a contract project manager you often get handed the trouble children of projects.
- Everywhere I see: Poor requirements Poor or no sizing
- People write poor requirements We have analysed 50,000 user stories Average size is 6 CFP Average LOC per CFP is 50 Average words per requirements is 10 Average words per LOC is 5 10 / 50x5x5 = 1:125 Opinions: Requirements = User stories Requirements != User stories As a contract project manager you often get handed the trouble children of projects.
- $78Bn USA wasted on project failures p.a.* Gartner USA 2018 Most people currently focus their efforts on testing the code. (and that the code meets the requirements) Capers Jones studies of thousands of projects shows other sources of defects need to be addressed. The ScopeMaster tool uncovers defects in requirements area and consequently reduces defects in other areas of your projects. Currently there is no other tool available to do this. Scopemaster sits alongside other tools and addresses a gap in identifying defects in this space/beyond the code. By finding and fixing quality problems early on, Scopemaster delivers projects faster, better quality (outcome) and improved value (as cost effectiveness).
- Requirements meetings can be time-consuming. Generally involve four or more people, (scrum team) (different roles on the project). Generally do not happen often enough to address all the issues. On average a scrum team could take a month to review and correct 100 user stories. In a business this would cost in the order of $25,000 in man hours. A trained user of ScopeMaster could achieve most of the correction work (50% or more) in 1-2 days.
- Card, Conversation, Collaboration Deliberately short on detail to force the conversation. Opinions: Requirements = User stories Requirements != User stories As a contract project manager you often get handed the trouble children of projects. Projects that are expected to be a problem or are already in trouble. I was doing OK and then I met Lonnie. one eyed man in the land of the blind I could really understand not only the state of a project but I could more rapidly work out what needed to be done. So thereafter I used FP on every project as the first thing I did. But counting FP is rather tedious and was often dismissed. So I set about trying to automate the counting of FP from requirements. And 18 months later ScopeMaster emerged. Eventually….
- If a user story can be interpreted in many ways, then it is likely to lead to mistakes. Consistent functional interpretation is key. Accommodates different phraseology Encourages clarity and conciseness Encourages user perspective
- Finding and defects normally takes 2-4 man hours at $50 per hour. $200. We find about 2 defects per user story = $400. Find & fix differential 400 - 20 = 380 Sizing reduced from $8- $3 per user story. Average size is 5CFP net benefit is 5x5=$25 per user story Knowing the size is at least $100 per CFP (10% average cost) => $500 per user story
- ScopeMaster can be used at any time in a project . Ideally, we would recommend that it is used at the outset and as requirements are evolving. Even to include as a best practice on all projects. Collaboration tools help the team work well as team. The most common tools used in this space, to help projects be successful. Coding tools are generally on the code itself and writing better code.
- Use cases: 2-4 hours per fp for BA writing req 8 is high User stories are easier to write. Double BA productivity Equivalent to $100k each p.a. $50m benefit per annum Measure faster ( Measure - use ISO FSM, without learning it Finds ±50% of requirements defects, before coding Performs testing that might not get done Promotes FSM adoption, which is good practice Encourages/teaches people to write good user stories Requirements arbiter Improve outsourcing contract management Gets your software to market faster Fewer failed projects HCL 500 BAs Infosys 800 BAs
- The most important aspect of any user story is to be very clear on these three words. If a FUR has multiple functional processes (steps) then ScopeMaster will look at all of them.
- If you don’t find the defects until coding has started or later it will cost even more! How many stories do you develop? How many teams What are the problems for you? How many analysts How many applications Do you Insource vs Outsource
- Cohesion the degree to which the elements inside a module belong together. In one sense, it is a measure of the strength of relationship between the methods and data of a class and some unifying purpose or concept served by that class
- Cohesion the degree to which the elements inside a module belong together. In one sense, it is a measure of the strength of relationship between the methods and data of a class and some unifying purpose or concept served by that class
- Portfolio Report
- Everywhere I see: Poor requirements Poor or no sizing
- NIST recognise the aspiration of COSMIC as an attempt to provide a a canonical reference for what a function point is https://www.gao.gov/new.items/d093sp.pdf Use cases were great with IFPUG User stories are insufficient for IFPUG productivity is un reasonable because it’s an interval scale. Cosmic FSM is a ratio scale, productivity measures are more valid. ize Most significant factor Inconsistent metrics IFPUG 1. Negative attitudes 2. Ideally know all requirements up front 3. Know the RETs, Know the DETs, Agilons (averaging) COSMIC Ideal for Agile Cosmic is mandatory for polish government projects > 2m euros. US government accounting office GAO recommends COSMIC in most circumstances March 2009. GAO-09-3SP 125-146 “COSMIC points were used if functional user requirements are known and the application is for business, real-time, embedded, or infrastructure software.”
- Canadian Security Software supplier 24 tasks from nine iterations
- The most important aspect of any user story is to be very clear on these three words. If a FUR has multiple functional processes (steps) then ScopeMaster will look at all of them.
- If you don’t find the defects until coding has started or later it will cost even more! How many stories do you develop? How many teams What are the problems for you? How many analysts How many applications Do you Insource vs Outsource