Pitfalls Of Software Development: What every Executives Should Know

100 %
0 %
Information about Pitfalls Of Software Development: What every Executives Should Know
Technology

Published on October 8, 2009

Author: mjdrouin

Source: slideshare.net

Description

Presentation done at the October 2009 Video Services Forum (VSF) meeting in Charlotte, NC. It provides a very high-level description of the two main problems for the success of Software Development projects: Requirements and Costing. It concludes with the upcoming trends and technological impacts for future software developments

Pitfalls of Software Development: What Every Executive should Know Marie Josée (MJ) Drouin @ VSF 09/10/07 mjdrouin@gmail.com

Who am I? • Director with 15 years of Media experience, I lead technical teams of up to 30 people and 3 managers to deliver most aspects of the business - Operations, Customer Services, Information Technologies, Project Management, Engineering, and Procurement. I developed expertise in managing cable, wireless, satellite, transmission, engineering and software development. I worked at Bell, Teleglobe, Intelsat, CBC and as a expert consultant. • Professional Engineer, Masters in Technological Management, ITIL foundation, PMP • I have extensive experience in speaking since the 90's (ouf!), subjects were always a mix of technologies, commerce and management. • Past engagements were: 8 weeks on Twitter: I love it! (2009), The Future of Broadcast Archive Systems (2008), DVB-H: Video over IP goes Wireless (2006), HDTV distribution (2005), Video over IP (2004) and, Several broadcast technical training (1994-1998): Video 101, Digital Video and Compression 201, Video testing techniques 301. • http://www.linkedin.com/in/mjdrouin • http://twitter.com/mjdrouin 09/10/07 VSF October 2009, Charlotte, NC 2

Pitfalls of Software Development? 1. Requirements 2. Costing 3. Technology 09/10/07 VSF October 2009, Charlotte, NC 3

Software is everywhere 09/10/07 VSF October 2009, Charlotte, NC 4

Standish Group – Software Projects 09/10/07 VSF October 2009, Charlotte, NC 5

Pitfalls of Software Development? 1. Requirements 2. Costing 3. Technology 09/10/07 VSF October 2009, Charlotte, NC 6

Requirements: What do you need? 1. Power users 2. Priority management 3. Plan releases 4. Links to other systems 09/10/07 VSF October 2009, Charlotte, NC 7

Access to power users • From the start • Throughout the project • Participate to discovery & concept design • Improve creativity as a member of the team Secret: • Spot-check and regularity • Team 09/10/07 VSF October 2009, Charlotte, NC 8

Waste: Building what you don’t need Usage of Features and Functions in Typical System Source: Standish Group Study of 2000 projects at 1000 companies 09/10/07 VSF October 2009, Charlotte, NC 9

Priority Management • Business Value vs Development Efforts • Feature sets • Focus: Start Small • Incremental development Secrets: • Data entry features • Functionalities – core business • Reports and retro-action features, afterward • Avoid hard-coded processes 09/10/07 VSF October 2009, Charlotte, NC 10

Release Management • Start small, choose only major features • Redo priority before each release • Keep a living list of desirable features • Can’t know what you’ll need • By using it, users will find new features Secret: • Don’t just replace what you have 09/10/07 VSF October 2009, Charlotte, NC 11

Links to other Systems • Web services • API • Shared dB Secret: • Business team need to think of their data and links between them 09/10/07 VSF October 2009, Charlotte, NC 12

Pitfalls of Software Development? 1. Requirements 2. Costing 3. Technology 09/10/07 VSF October 2009, Charlotte, NC 13

Costing 1. Easy evaluation: Cost units 2. Knowledge Bases 3. Cost risk factors 09/10/07 VSF October 2009, Charlotte, NC 14

Cost Units • Every aspects of every feature • Every screen • Every click for every System involved + a % for: • Analysis, specifications, design • Planning, PM • Test, test, test • Implementation 09/10/07 VSF October 2009, Charlotte, NC 15

Cone of uncertainty Defect cost increase Cocomo KNOWLEDGE BASES 09/10/07 VSF October 2009, Charlotte, NC 16

Cone of Uncertainty 09/10/07 VSF October 2009, Charlotte, NC 17

Defect cost increase 09/10/07 VSF October 2009, Charlotte, NC 18

Cocomo II 09/10/07 VSF October 2009, Charlotte, NC 19

Cost Risk Factors • Team quality, experience and discipline • Software development best practices • Business targets ≠ estimates • Rewrite code = 100% cost increase • Planning and Risk Management: Plan for rework and monitor it • Focus on quality and costs rather than schedule • Licence agreements Secret: Other systems! 09/10/07 VSF October 2009, Charlotte, NC 20

Pitfalls of Software Development? 1. Requirements 2. Costing 3. Technology 09/10/07 VSF October 2009, Charlotte, NC 21

Technology 1. Technology debt 2. Human factors 3. New trends 09/10/07 VSF October 2009, Charlotte, NC 22

Technology Debt • Teams skills –Coding language experience –Maintenance and operations • Stability and complexity of ancillary systems • Maturity of technology 09/10/07 VSF October 2009, Charlotte, NC 23

Human Factors • Technologies change but concepts, design and architecture stays • Team knowledge and professionalism makes more difference than chosen technology • Practice makes perfect • Reuse of existing code, systems, data • Simplicity 09/10/07 VSF October 2009, Charlotte, NC 24

New Trends • Open-source • Social media: Web 2.0 • Linked and structured data: Web 3.0 • Real-time • Mobile • Personalization, filtering • Privacy • Security • Internet of things 09/10/07 VSF October 2009, Charlotte, NC 25

Conclusions 1. Manage Priorities – Start Small 2. Get involved - Vision 3. Cost in stages - Plan releases 4. Focus on Quality People – People - People 09/10/07 VSF October 2009, Charlotte, NC 26

Questions? 09/10/07 VSF October 2009, Charlotte, NC 27

Add a comment

Related presentations

Presentación que realice en el Evento Nacional de Gobierno Abierto, realizado los ...

In this presentation we will describe our experience developing with a highly dyna...

Presentation to the LITA Forum 7th November 2014 Albuquerque, NM

Un recorrido por los cambios que nos generará el wearabletech en el futuro

Um paralelo entre as novidades & mercado em Wearable Computing e Tecnologias Assis...

Microsoft finally joins the smartwatch and fitness tracker game by introducing the...

Related pages

Pitfalls Of Software Development: What every Executives ...

Pitfalls Of Software Development: What every Executives Should Know ...
Read more

10 acquisition pitfalls IT should watch out for - TechRepublic

10 acquisition pitfalls IT should watch ... delivered to your inbox every ... Product Research and Software Development for Summit ...
Read more

The 5 Pitfalls of Estimating a Software Project ...

It took until I was 6 years into my career to learn the art of estimating a software ... to software development. ... should know better ...
Read more

5 common pitfalls of CICD -- and how to avoid them | InfoWorld

... Build security into software development. ... the software should be broken into smaller components ... Technology executives know that ...
Read more

Five Things Every Software Executive Should Know About Scrum

Five Things Every Software Executive Should Know ... for Agile software development and is ... important things software executives should ...
Read more

What executives should know, but often don’t, about risk ...

What executives should know, ... What I call ‘risk intelligent management’ allows executives and ... Shetty has worked in the software industry ...
Read more

Keynote Addresses | Construx

Keynote Addresses. Steve McConnell is a ... SEVEN DIAGRAMS EVERY SOFTWARE PROFESSIONAL SHOULD UNDERSTAND ... do we know which software development ideas ...
Read more

What do CEOs do? A CEO Job Description. | Stever Robbins

Many don’t know what their job should be, ... Every dollar you raise and spend should produce more than $1 of ... What do CEOs do? A CEO Job Description.
Read more