1. Development and Quality Plans Chapter 6

2. Introduction Project managers prepare –development and –quality plans. Onerous (مرهق) task, –Senior level management on one end and –Developers on the other Two dance to different drummers. These plans are vitally important to meet contractual commitments (للوفاء بالالتزامات التعاقدية)

3. Objectives of development and quality plans Elements of development plans Elements of quality plans Major software risks Process of software risk management Importance of development and quality plans for small projects Importance of development and quality plans for internal projects. Lesson Objectives

4. Planning is meant to prepare adequate foundations for successful and timely completion of the project. The planning process includes: 1.Scheduling development activities and estimating the required manpower resources (الموارد البشرية) and budget 2.Recruiting team members and allocating development resources 3.Resolving development risks 4.Implementing required SQA activities 5.Providing management with data needed for project control 6.1 Development Plan and Quality Plan Objectives

5. Each of the following 11 components of a development plan are appropriate to different parts of a project. 1. Project Products, specifying “deliverables” Critically important. Must decide on deliverables! dates and items installation site – local or physical install training – customer service dates, participants, and sites (much is done on line now…) 6.2 Elements of the Development Plan

6. 2. Project Interfaces How does the new software interface with existing software? –(major consideration in large corporation) How does the software affect other parts of a larger system or similar systems?? Any hardware considerations for interfacing? Special hardware? 6.2 Elements of the Development Plan

7. 3. Project methodology and development tools for various phases during development, maintenance. Heuristic (ارشادي): never use untested tool / methodology on a new project with high visibility!! Methodology must be decided upon. –Usually organizations have ‘established’ ways of proceeding… Implementation tip –When evaluating the suitability of proposed project methodology and development tools, one should also take into account the professional experience of the staff, including the subcontractors’ personnel, even if temporary. 6.2 Elements of the Development Plan

8. 4.Software Development Standards and Procedures Must be conventions!! Standards and Integration!! a MUST! –A list should be prepared of the software development standards and procedures to be applied in the project. 5.Project Milestones completion dates, products clearly define. Must synchronize with Overall Plan. More detailed than Overall Plan More detailed than iteration plans –For each milestone, its completion time and project products (documents and code) are to be defined. 6.2 Elements of the Development Plan

9. 6.Laying out the Development Process Define the project’s phases Planning: inputs/outputs/activities/activity duration/sequence and dependencies/resources needed for each activity/ design reviews/ testing/ training for customer support/ more… GANTTT Charts / CPM, PERT all include sequence dependencies and duration. Microsoft Project and Rational Conductor 6.2 Elements of the Development Plan

10. 7. Project Staff Organization Organizational structure – teams, tasks, sub contractors, temporary workers. Pecking order… much risk! –Professional requirements: professional certification, experience in a specific programming language or development tool, experience with a specific software product and type, and so forth. –Number of team members required for each period of time, according to the activities scheduled, and team size varies from beginning to fully staffed. –Designate team leaders and members team composition will change throughout a long development effort. staff reassignments (الانتداب); illness, ….. 6.2 Elements of the Development Plan

11. 8. Development Facilities (Very important) –Hardware, software, tools, development environments, training on these, space –For each facility, the period required for its use should be indicated on the timetable. –Many very nice facilities nowadays – break rooms, ping pong; nice coffee / beverage facilities; day care. 9.Control Methods –How to control the monitoring process / reporting process with respect to plans, test reports, reviews, how goes it, and more. 6.2 Elements of the Development Plan

12. 10.Project Cost Estimation –Project cost estimates are based on proposal costs estimates, followed by a thorough review of their continued relevance based on updated human resource estimates, contracts negotiated with subcontractors and suppliers, and so forth. human resource estimates, contracts with suppliers, internal development and unavailability, budget changes, risk considerations. travelfirst go go trainingsecond to go… 6.2 Elements of the Development Plan

13. 11.Development Risks - Inherent (متأصل) in any project Risk: “a state or property of a development task or environment, which, if ignored, will increased the likelihood of project failure.” Typical development risks are: –Technological gaps – Lack of adequate and sufficient professional knowledge and experience to carry out the demands of the development contract. –Staff shortages – Unanticipated shortfalls (عجز غير متوقع) of professional staff. –Interdependence of organizational elements –Environmental risks –Budget risks 6.2 Elements of the Development Plan

14. 1.Developing wrong software functions * 2.Unrealistic schedules and budgets* 3.Developing wrong user interface 4.Gold plating* 5.Continuing stream of requirement changes* 6.Shortfalls in externally furnished components 7.Shortfalls in externally performed tasks 8.Personnel shortfalls* 9.Real-time performance shortfalls* 10.Straining computer science capabilities

15. Pre- project Risk identification and assessment Planning risk management activities New project Planning and updating risk management activities Implementing risk management actions (risk resolution) Monitoring software risk management activities Identifying and assessing new software risks Ongoing projects Evaluate monitoring results Required results achieved Unsatisfactory results

16. 1. List of quality goals These refer to the quality requirements in the developed software system. Quality goals should reflect the major acceptance criteria found in the requirement’s document (an RFP) correctness, reliability, robustness, maintainability…. RFP is often used to measure successful achievement of the customer’s quality requirements. 6.3 The Elements of a the Quality Plan

17. Example A software system to serve the help desk operations of an electrical appliance manufacturer is to be developed. The help desk system (HDS) is intended to operate for 100 hours per week. The software quality assurance team was requested to prepare a list of quantitative quality goals appropriate to certain qualitative requirements, as shown in Table 6.1.

18. 2. Planned Review Activities The planned reviews should include a listing of all reviews. design reviews technical reviews managerial reviews code inspections (فحص، مراقبة) Pros and Cons…………………… All reviews need to include: Scope – what does it cover Type – emphasis – managerial, technical, super detailed… Schedule – often based on previous reviews and outcomes Procedures – action lists; present and discuss; … Who is to attend? Collateral interest?? ***** Responsibilities for review; documents needed, by when… 6.3 The Elements of a the Quality Plan

19. 3. Planned Software Tests Must include a complete list of planned tests Each test must include the following: coverage of test: unit, integration, system, subsystem…. type of test: may include computer-generated tests and their application via test suites, and more Planned test schedule – prioritized and follow up Exact procedures (for different types of tests…) Who is responsible for carrying out tests notification, time, date, materials, facilities, etc… Different people responsible at different times!! ** 6.3 The Elements of a the Quality Plan

20. 4. Planned Acceptance Tests for Externally Developed Software A complete set of acceptance tests to be run for externally developed software must be provided within the quality plan! (Complete set must be run for our own developed software!) Especially critical for purchased software, contracted software, customer-supplied software. These tests can be run in parallel with internally-developed software tests (tests that internally are developed to supplement other tests) 6.3 The Elements of a the Quality Plan

21. 5. Configuration Management The quality plan MUST include configuration management tools and procedures for managing the software configurations, versions, etc. Must be an intrinsic part of the entire project! The Quality Plan may be included within the Development Plan or as an independent document. The document, however compiled, must be reviewed and approved by the organization’s standard approval process. 6.3 The Elements of a the Quality Plan

22. Does a project of only 40 working days’ duration, to be performed by one professional and completed within 12 weeks, justify the investment of a man-day in order to prepare full-scale development and quality plans? Does a project to be implemented by three professionals, with a total investment of 30 man-days and completed within five weeks, require full-scale plans? Development / Quality Plans for Small and Internal Projects

23. Quality plans for small projects Cases/situations where neither development nor quality plans are required, e.g. projects requiring 15 man-days. Cases/situations where the decision to prepare the plans is left to the project leader’s discretion. One example could be a project requiring less than 50 man-days where no significant software risk item had been identified – in this case it might be decided that no plans will be prepared. Another example could be a small but complicated project that has to be completed within 30 days, in which there is a heavy penalty on not being completed on time. In this case, planning is needed in order to cope with the project difficulties. Cases/situations where development and quality plans are obligatory.

24. Lots of issues here… Sometimes not done due to short duration / manpower Sometimes planning is left up to the project leader’s discretion. Perhaps a critically-important and high risk but short duration effort with high-penalty shouts for a plan… Sometimes, via contract, both development and quality plans are simply required. Development / Quality Plans for Small Projects

25. Several advantages to planned over unplanned projects: 1.A more comprehensive / thorough understanding of the task is likely (gained when developing the plan) 2.Greater responsibility for meeting obligations can be assigned, as they can be ‘seen’ more clearly since articulated (who does what) 3.Easier to share control of the project and identify unexpected delays (any plan better than no plan at all!) 4.Better understanding of requirements and timetable can be reached between customer and developer. Development / Quality Plans for Small Projects

26. Lots of projects done for the internal use of organization. Here, normally no external body is a customer Can be medium or large scale. Tendency to avoid adequate development / quality plans avoiding plans is fraught with errors. cost overruns, finger pointing, missed dates, internal friction among cooperating shops, … Often put on back burner!! Development / Quality Plans for Internal Projects

27. Internal Customers ‘can’ enjoy advantages. smaller deviations from planned completion dates smaller budget overruns better control over development process – problems can be addressed locally, Organizationally, reduced risk of market loss (done for internal use) reduced risk of litigation (late arrival; non-compliance) reduced risk of impairing a firm’s reputation reduced risk of requesting a budget supplement. Preparing Plans provides Advantages