1 project management in software engineering project initiation what to do? why to do?

36
1 Project Management in Software Engineering Project initiation What to do? Why to do?

Upload: florence-ferguson

Post on 13-Dec-2015

217 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

1

Project Management in Software Engineering

Project initiationWhat to do?Why to do?

Page 2: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

2

Plan

1. Preconditions for project initiation

2. General risks associated with the projects

3. Identification of needs and objective

4. Finding and analysis of the project objective

5. Resource analysis (including finances)

6. Project charter

7. Composition of the project team

Page 3: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

3

The aim of the project initiation phase

Form a clear understanding about the rationality of project planning –

answer the question

“Would planning of a project be reasonable?”

Page 4: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

4

The main tasks for project initiation phase

1. Make sure that the preconditions for project initiation are fulfilled.

2. Define the project objective (what to do?)

3. Make sure about the necessity of the project (why to do?)

4. Make sure about feasibility of the project (whether the achievement of the project’s objective is realistic?).

The main instrument for decision – project charter.

Page 5: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

5

Preconditions for project initiation

1. Existence of a problem (that the project could solve).

2. Existence of some ideas how the problem could be approached.

3. The project (that is, solving the problem) supports achieving long-term objectives of the institution (Example: Tempus).

4. Necessary human resources are available (competence + quantity). Example: N: LeFlow eParticipation (Interreg IV A).

5. Financing probability is big enough (compare with the possible competitors). Example: low success rate of personal research grants.

6. Requirements and limitations are clear (Example: 1. round of structural funds was announced while regulating documents were not ready).

7. Risks associated with the projects are bearable.

Page 6: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

6

General risks associated with the projects

1. Unreasonable spending of resources. Example: unsuccessful project application LeFlow: Competency Management and Learning Flows within Mash-up Personal Learning Environments.

2. Infiltration of ideas to the competitors. Example: school of social sciences.

3. Damage of reputation. Example: transfer of JEP 11202 management to another university.

4. Deterioration of the quality of other activities. Example: too many EU FP6 projects were approved.

5. Poor acceptance/exploitation of the outcome of the project by the custo-mers (bad user friendliness, similar products of the competitors, …).

6. Damage that is caused by the partners. Example: bankruptcy because of partners’ failure.

Page 7: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

7

Possible alternatives

1. Outsource a Project Plan. Example: Layers (Invent Baltics).

2. Outsource the intended outcome of the project. Example: TLU web.

3. Outsource some activities of the project. Example: software engineering for eParticipation project; collecting empirical data for R&D projects.

4. Becoming a partner of another relevant project (possibly of another institution).

Page 8: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

8

Opportunities that may open through projects

1. Getting resources for development of the Institution. Example: about 50% of the income of the School of Digital Technologies is project based.

2. Capacity building of the institution. Example: DoRa professors and postdocs, ID lab, HITSA tiger university projects, …

3. Advancement of organizational culture. Example: following the fixed budgets and deadlines.

4. Raising the reputation of the institution.

5. Widening the network of partners.

Page 9: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

9

Recommendations 1 (Preconditions for project initiation)

1. Decision about a project initiation should base on a balanced analysis of risks and opportunities: sometimes it is reasonable to initiate a project even if some risk or even losses are obviously too big. Example: construction of Mare building of Tallinn University (Eesti Ehitus).

2. For reducing the risks of failure: Before managing a project, participate on a project as a member Before managing a big project, manage a small one Before managing an international project, manage a national Before managing an international project, participate as a team

member

Page 10: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

10

Identification of needs

Needs: a (desirable) situation or object that supports functioning of a system or achieving a goal.

Needs of a project depend on the gap between the current situation and desirable situation.

Problem: modeling and estimating/predicting!

Maslow’s hierarchy of human needs (1943):

NB! Satisfaction of lower level needs should precede to those of the higher level.

Problem: (the decision makers) are not always

able/willing to recognize the actual needs.Physiological needs

Safety needs

Love and belonging

Esteem

Self-actualization

Page 11: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

11

Hierarchy of ICT needs – an example

Hierarchy of ICT needs (R. Urwiler, M. Frolick, 2008):

1. Infrastructure needs

2. Security & stability needs

3. Integrated information needs

4. Competitive differentiation needs

5. Paradigm shift (innovation excellence)

NB! Again five levels.

Page 12: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

12

General hierarchy of needs

1. Existential (needs that enable usage of a product or service).

2. Business continuity (allows the smooth functioning).

3. Relevance (incl easy of use).

4. The quality compared to other similar solutions (allows to ensure competitiveness).

5. Innovation (will ensure sustainability).

Page 13: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

13

Fundamental in initiating a project – specification of the main objective

Page 14: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

14

Project objective

Project objective is the key factor that determines the planning (and execution) of a project.

The requirements for objectives – SMART:

1. Specific – tells exactly what is expected.

2. Measurable – concrete criteria for measuring progress (E: bank image).

3. Agreed (attainable) – stakeholders recognize its importance.

4. Realistic (relevant) – enough resources are available.

5. Time-bound (timed, timely) – grounding within a time frame.

SMART requirements can be applied for sub-goals as well.

Finding a good project objective needs discussions involving other stakeholders and is often time consuming.

Page 15: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

15

Analysis of project objective – the factors

Forward looking! Analysis of possible trends.

Taking into account the current and emerging factors, requirements and limitations :

1. Changes in the market (E: digitalization, open content)

2. Institutional problems and possible reorganizations

3. Possible changing of consumer needs

4. Changes of technological solutions (E: cloud solutions)

5. Emerging/changing of social demand (E: increase of elderly people)

6. Legislative constraints (E: role of employers in curriculum development)

7. Possible activities of the competitors (E: Science School, Student Academy).

Image of a sandglass: absorb as much knowledge as possible (upper part) for serving the interests of as many as possible individuals (lower part).

Page 16: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

16

Recommendations 2 (specification of the objective)

1. Discuss the needs and objective with the main stakeholders (including target groups):

• Potential users of the expected outcome of the project,

• Bosses and colleagues,

• Potential donors and contributors,

• Project team members.

Example: Consultations in the ministry during the preparations of Educational Technology master programme.

2. Find effective/appealing name and acronym for the project.

Page 17: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

17

Exercises – preconditions and objective

1. Name additional risks (including those of the decision makers).

2. What are the weaknesses of these formulations of the objective:

a) “Studying diffusion processes in multiple-component systems”,

b) “Development of an optimal methodology for medical treatment of cold”.

3. Name additional factors that can be taken into account by finding the objective of a project.

4. What SMART principles are not satisfied and why by the following titles of student‘ theses: a) Development of a full-featured learning management system for

secondary schools; b) Finding an optimal route between two arbitrary locations in Kabul;c) Development of a web page.

Page 18: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

18

Exercises – preconditions and objective

1. Bring an example of a computer software you need but that is currently not available.

2. For finding an objective, balanced scorecards can be used. What aspects are assumed to be taken into account (for a definition of balanced scorecards, see, for example www.balancedscorecard.org)?

3. List services that are needed, but not yet recognised enough in the society.

4. List services importance of what is recognised, but that are nevertheless not offered enough.

Page 19: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

19

Finding sources of financing

Ability to get and deploy resources is one of the main quality indicators of project managers.

Financing (and the application procedures) depends on the type of the: applicant – an institution or an individual application – regulated (form based) or not context – in house, belonging to a program, sponsored

Decisive aspects: Belonging to priority areas (E: Tempus IT master curricula) Eligibility of the applicant (E: Tiger University program – public universities) Fulfilling the formal requirements (if there are any. E: SF first call) The interests of the sponsor (by sponsored non-regulated projects).

Page 20: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

20

Some principles of looking for a sponsor

The main aim of a sponsoring institution – improve its image.

1. Present your application as an offer for investments, not as asking for a charity.

2. Follow the wishes and suggestions of the potential donor (interests dominate over logic); listen the sponsor (E: ISE; financing doctoral studies).

3. Compare your institution in relation to the competitors.

4. Make your case bigger than your institution.

5. Few will do the most.

6. Inform about your plans without asking support.

7. Patience will succeed.

8. Relations with the donors should be kept after completion of the project.

Page 21: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

21

Sponsoring – practicalities

Agreements:

1. How (if at all) will the sponsorship publicly announced (E: Balteco),

2. How (if at all) the sponsorship can be used by partners in their PR-activities,

3. What other sponsors (if at all) does the sponsor accept,

4. ...

Ingrid Vuks (some results from the master thesis):

1. sponsoring is not regulated in ¾ of Estonian enterprises,

2. Sponsoring principles are not public (only 3 out of 200 had them in the Web),

3. A decision making body can be very different.

The most effective practice in Estonia – personal acquaintance.

Page 22: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

22

Recommendations 3 (sources of financing)

In finding the sources of financing:

Be informed (E: status of Estonia in EU 5FW e-learning projects)

Evaluate your chances compared to the potential competitors

Trust, but make sure – Lenin: “доверия это хорошо, но

контроль лучше” (“Trust is good, but control is better”).

Example: Humboldt research grant.

Page 23: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

23

Exercises – financing projects

1. In what cases each of the strategies below will work better: a) First determine an objective for a project and then search for finances,

b) First determine a donor and then the objective for a project.

2. What of the principles of looking for a sponsor are in your opinion more important to follow, and what maybe not so important? Bring examples of cases where these principles (or some of them) are followed and where not.

3. Place yourself in the role of a sponsor. What arguments would for you be the most decisive for a positive decision?

Page 24: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

24

Exercises – financing projects 2

1. Choose an institution that finances projects and analyse statistical data of successful projects (distribution by subject areas, amount of support, duration etc).

2. Find answer to the following questions concerning the objective of the project of your group:

• What are success indicators of the project?

• What are the strengths of the project team?

Page 25: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

25

Resource analysis

1. Are enough qualified people available?• Uncertainty in a project start (involvement of potential experts; 6FP: 2/8;

targeted projects; LeFlow+eParticipation);

• organizational type of the institution (functional, project based, matrix type).

2. Is necessary infrastructure available (workplaces, tools)?

3. Does the upper management, partners etc accept the project initiation/needs? E: Estonian Educational IS.

4. In case the project will receive insufficient financing, are there necessary compensation opportunities? 100%/0% model.

Page 26: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

26

Recommendations 4 (estimating the work load)

1. Jobs that require specific competence (which is not available in the project team) is recommended to outsource.

2. For large and complicated projects, it is recommended to hire a full-time project manager. Examples: Enterprise Estonia SPINNO project – Knowledge Transfer Centre, Centre for Educational Innovation.

Page 27: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

27

Project charter

Content: short (1-2 pages) description of the basic information of the project (name, objective, needs estimation, novelty, deliverables/activities, partners, resources, duration).

The aim: Get acceptance from decision makers Finding partners Agreeing on the role distribution between the partners

Possible additional aspects depend on the type of the project: constraints, standards, examples of similar projects, exploitation of project outcome etc.

Example: Quality system of ICT vocational schools (Appendix 1 of LN).

Instead of one document, there can be two or three. PRINCE2: a) Project Mandate; b) Project Brief; c) Project Initiation Document.

Page 28: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

28

Composition of a project team

1. Most important – motivation of the partners. E: change of a partner in TEMPUS math.curr. project.

2. Partners having experience in similar projects are preferred.

3. Leading institutions are preferred (quality, mediated contacts, reputation).

4. Prefer partners with whom you already have had good cooperation.

5. Partners’ specific interests should not dominate over project’s objectives. E: covering study costs for master studies.

6. Partners should complement each other. E (of risks): a person in a partner institution left to another institution (AGETT).

7. The partners should accept the conditions set by the sponsors. E: a partner demanded double salary (AGETT).

Page 29: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

29

Important aspects of partnership

Possible problems in becoming a partner: Your work and competence will not adequately be exploited; Incompetent co-ordination of the project can harm the reputation

of partners; Different understanding and interpretations. E: prototyping in

realisation of innovation vouchers.

Insufficient acceptance by partners of the project manager can harm the project.

Formal requirements: North-South (EU projects), minimal number of partners, involvement of PhD students, ...

Page 30: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

30

Indicators of a risky partner

1. Focused on getting projects accepted, not so much running them.

2. Not taking responsibilities.

3. Dominating “know-it-all” people.

4. Formalists who are valuing documents, not so much the real activities/outcomes.

5. Having “fuzzy” tasks. E: different people attend the meetings.

6. Do not hold agreements.

7. “Last minute” executors (NB! Quality risk).

Page 31: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

31

Recommendations 5 (partners)

1. Find an optimal number of partners:

a) Too many partners will make the administration of the project very clumsy,

b) Too few partners may harm the quality of the project.

2. For ensuring the quality of the project, most important are the people rather than the institutions these people are working in.

Page 32: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

32

Exercises – finding partners

1. What signs will indicate that a partner is not motivated enough? How the lack of motivation and incompetence can be distinguished?

2. Assume you have to choose between two partners; one is a top expert but not very interested in the project, the second is almost unknown but very motivated. In what circumstances would you prefer the first (correspondingly, the second) partner? What are the main risks in both cases and how would you deal with these risks?

3. In what cases is it reasonable to involve a leading institution even if is not motivated enough?

Page 33: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

33

Exercises – project charter

1. Analyze an unsuccessful project and describe the main factors that caused the failure.

2. Using web search with the keywords “project mandate”, “project brief”, “project charter” and “project initiation document”, study descriptions of at least three projects.

3. Analyze the charter presented in the Lecture Notes (Appendix 1). What aspects could be described more thoroughly there?

Page 34: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

34

Home assignment No 1

1. Formulate an objective of a project that can be planned and completed by a group of 3-4 students during 9-10 weeks.

2. Assess your personal competences according to the elements 6.1 … 11.5 of PMCD Framework.

Find (out of 25):o Your five greatest strengthso Your five greatest weaknesses.

Page 35: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

35

Next lecture:

Friday, September 18

Topic:Project planning. Forming project teams

Page 36: 1 Project Management in Software Engineering Project initiation What to do? Why to do?

36

Examples of professions of the future (Mike Walsh)

www.mike-walsh.com/media/bid/52468/Top-10-Professions-Of-The-Future:

• Data Scientist

• Tech Addiction Counseller

• Enterprise Anthropologist

• Virtual Girlfriend

• Pattern Recognition Specialist 

• Net Star

• Brand Storyteller

• Freelance Work Agent

• Cyber-Warfare Operative

• Professional Video Gamer