Garantie de satisfaction à 100% Disponible immédiatement après paiement En ligne et en PDF Tu n'es attaché à rien
logo-home
Complete overview/summary per week for Project management: Book, (guest)lectures, articles, $4.49
Ajouter au panier

Resume

Complete overview/summary per week for Project management: Book, (guest)lectures, articles,

 9 fois vendu
  • Cours
  • Établissement
  • Book

Week 1 – Introduction - Rigby et al (2016) Week 2 – System development - Brooks (1987), Boehm (1988), Jarke et al (2011) Week 2 – Requirements Engineering Week 3 Business case & Metrics - Bacon (1992) Lecture 3 – Software cost estimation Week 4A Agile & Devops Dyba, Dingsoyr & Moe (20...

[Montrer plus]

Aperçu 4 sur 154  pages

  • Oui
  • 23 février 2021
  • 154
  • 2019/2020
  • Resume
avatar-seller
CONTENTS

Week 1 – Introduction - Rigby et al (2016) ................................................................................................... 6
Week 1A Sheets ........................................................................................................................................ 6
Devils triangle – Project success ........................................................................................................... 6
Standish Group Chaos Report success factors ...................................................................................... 7
Agile ...................................................................................................................................................... 8
Why Agile Now (Rigby).......................................................................................................................... 8
Or… is it only a fashion (Cram and Newell, 2016) ................................................................................. 9
Rigby et al (2016) – Embracing Agile ........................................................................................................ 9
Week 1B Sheets ...................................................................................................................................... 13
(Elias Committee, 2014) Why is Developing IT for Government hard ................................................ 13
Design cycle......................................................................................................................................... 13
Waterfall ............................................................................................................................................. 14
System Development Lifecycle ........................................................................................................... 14
Iterative, Incremental ......................................................................................................................... 15
Spiral model ........................................................................................................................................ 15
Back to Agile (Principles) ..................................................................................................................... 16
Scrum .................................................................................................................................................. 16
XP Extreme Programming ................................................................................................................... 16
Planning............................................................................................................................................... 17
Scheduling ........................................................................................................................................... 17
Conclusions ......................................................................................................................................... 17
Week 2 – System development - Brooks (1987), Boehm (1988), Jarke et al (2011) .................................. 18
Week 2 – Software development ........................................................................................................... 18
Use Case Diagram (UML) .................................................................................................................... 18
Requirements ...................................................................................................................................... 19
Elias committee recommendations to improve ICT project for government ..................................... 19
Requirements engineering joke .......................................................................................................... 19
Design as a dialogue............................................................................................................................ 20
Brooks (1987) No silver bullet, essence and accident in software engineering ..................................... 21
Abstract ............................................................................................................................................... 21

, essential and accidential difficulties – 2 types of complexity ............................................................. 21
Complexity .......................................................................................................................................... 22
Conformity .......................................................................................................................................... 22
Changeability....................................................................................................................................... 23
Invisibility ............................................................................................................................................ 23
How to address these issues? ............................................................................................................. 24
How to address complexity? ............................................................................................................... 24
Boehm (1988) A spiral model of software development and enhancement ......................................... 25
Week 2 – Requirements Engineering...................................................................................................... 29
Verification and Validation ................................................................................................................. 29
Requirements and Testing (V-Model of testing)................................................................................. 29
Requirements enigneering Boehm 1979 ............................................................................................ 30
Conclusions ......................................................................................................................................... 30
Jarke et al (2011) The brave new world of design requirements ........................................................... 31
Abstract ............................................................................................................................................... 31
Introduction – What is requirement engineering ............................................................................... 31
Requirements research – a brief overview ......................................................................................... 32
Methodology – Challenges in requirements engineering................................................................... 32
The changing nature of requirements ................................................................................................ 33
Four requirement principles ............................................................................................................... 34
Comparisons with conventional RE practices ..................................................................................... 37
Week 3 Business case & Metrics - Bacon (1992) ........................................................................................ 38
Lecture 3 – Business case........................................................................................................................ 38
Developing a business case................................................................................................................. 38
Schwalbe p.99 ..................................................................................................................................... 49
In practice – What are the hidden costs drivers of cloud migrations at banks .................................. 50
Portfolio management ........................................................................................................................ 50
Bacon (1992) The use of decision criteria in selecting IS/Technology investments ............................... 51
Organizational learning ....................................................................................................................... 51
Financial criteria .................................................................................................................................. 52
Summary & Conclusion ....................................................................................................................... 53
Lecture 3 – Software cost estimation ..................................................................................................... 55

, Difference between costs and price ................................................................................................... 55
Project planning (Ch5) – Scope: What to do and what not to do ....................................................... 55
Development cost estimation (Ch6) ................................................................................................... 56
Software metrics – Complex complicated .......................................................................................... 57
Analogy estimates ............................................................................................................................... 57
Function points – Function point analysis (FPA) ................................................................................. 57
COCOMO (Boehm, 1981) – Constructive cost model ......................................................................... 59
Why not use machine learning for establishing historical analogy? .................................................. 60
Discussion en conclusion .................................................................................................................... 61
Week 4A Agile & Devops ............................................................................................................................ 62
Sheets 4A ................................................................................................................................................ 62
Agile .................................................................................................................................................... 62
XP (Beck, 1999) ................................................................................................................................... 63
Scrum (Schwaber & Beedle, 2002)...................................................................................................... 63
Scrum: roles ........................................................................................................................................ 64
Scrum: rituals ...................................................................................................................................... 65
Scrum: artefacts .................................................................................................................................. 66
Scrum: management tools .................................................................................................................. 66
Scrum: why does it work? ................................................................................................................... 67
Scaled agile – SAFE - LESS.................................................................................................................... 68
Agile and LEAN .................................................................................................................................... 69
Lean ..................................................................................................................................................... 70
Business process improvement .......................................................................................................... 70
Business process re-engineering (Hammer & Champy, 1993; Davenport, 1994) .............................. 71
DevOps ................................................................................................................................................ 71
How to deal with multi-speed IT developments? (Agile and Stable)(Möhlmann, 2016) ................... 73
Continuous change: really? (Brous & Janssen) ................................................................................... 73
Conclusions ......................................................................................................................................... 74
Dyba, Dingsoyr & Moe (2014) Agile Project Management ..................................................................... 75
Software project management ........................................................................................................... 75
Self-managing software teams ........................................................................................................... 76
Shared-decision making ...................................................................................................................... 77

, Principles of agile project management ............................................................................................. 78
Fitzgerald & Stol (2017) Continuous software engineering: A roadmap and agenda ............................ 80
Trends in the software engineering landscape ................................................................................... 80
Lean Thinking ...................................................................................................................................... 84
Continuous development ................................................................................................................... 85
Continuous *: continuous software engineering and beyond............................................................ 86
Week 4B – Stakeholders and support CH8 & Risk management CH7 (Bryson) .......................................... 88
Lecture 4B Stakeholders and support – power and politics Part 1......................................................... 88
Organizational structures (Chapter 4) ................................................................................................ 88
Case standard business reporting (XBRL) – Bharosa et al. (2015) ...................................................... 89
Impose with leeway – Bharosa et al (2011) ........................................................................................ 90
Collaboration in networks De Bruijn and ten Heuvelhof (2002)......................................................... 90
E3 value diagrams (AirBnB value network) (Gordijn and Akkermand, 2003) ..................................... 91
Distribution of revenues from a project – Sustainable business model ............................................. 91
Bryson (2004) What to do when stakeholders matter – Identification & analysis................................. 92
Coalition formation ............................................................................................................................. 92
An array of techniques ........................................................................................................................ 93
Lecture 4B Part 2 ..................................................................................................................................... 96
Power, politics and MIS implementation (Markus, 1983) .................................................................. 96
Stakeholders & Power interest grid and their interests case testvision ............................................. 97
Lecture 4B Risk management ................................................................................................................. 98
Risk ...................................................................................................................................................... 98
Being in control – Plan-Do-Check-Act (Deming, 1986) Learning from mistakes ................................ 99
Project risk identification .................................................................................................................... 99
Swot analysis; Fishbone diagram ...................................................................................................... 100
Designing control measures.............................................................................................................. 101
Qualitative versus quantitative risk analysis..................................................................................... 101
Risk appetite: Outcome of a dialogue ............................................................................................... 102
Monitoring and controlling the (software) project........................................................................... 102
Week 5 – Open source software development ........................................................................................ 105
Open source principles (opensource.com but shows in paper/lecture too) ........................................ 105
Raymond (1997) The Cathedral and the Bazaar ................................................................................... 106

Les avantages d'acheter des résumés chez Stuvia:

Qualité garantie par les avis des clients

Qualité garantie par les avis des clients

Les clients de Stuvia ont évalués plus de 700 000 résumés. C'est comme ça que vous savez que vous achetez les meilleurs documents.

L’achat facile et rapide

L’achat facile et rapide

Vous pouvez payer rapidement avec iDeal, carte de crédit ou Stuvia-crédit pour les résumés. Il n'y a pas d'adhésion nécessaire.

Focus sur l’essentiel

Focus sur l’essentiel

Vos camarades écrivent eux-mêmes les notes d’étude, c’est pourquoi les documents sont toujours fiables et à jour. Cela garantit que vous arrivez rapidement au coeur du matériel.

Foire aux questions

Qu'est-ce que j'obtiens en achetant ce document ?

Vous obtenez un PDF, disponible immédiatement après votre achat. Le document acheté est accessible à tout moment, n'importe où et indéfiniment via votre profil.

Garantie de remboursement : comment ça marche ?

Notre garantie de satisfaction garantit que vous trouverez toujours un document d'étude qui vous convient. Vous remplissez un formulaire et notre équipe du service client s'occupe du reste.

Auprès de qui est-ce que j'achète ce résumé ?

Stuvia est une place de marché. Alors, vous n'achetez donc pas ce document chez nous, mais auprès du vendeur MasterimK. Stuvia facilite les paiements au vendeur.

Est-ce que j'aurai un abonnement?

Non, vous n'achetez ce résumé que pour $4.49. Vous n'êtes lié à rien après votre achat.

Peut-on faire confiance à Stuvia ?

4.6 étoiles sur Google & Trustpilot (+1000 avis)

63950 résumés ont été vendus ces 30 derniers jours

Fondée en 2010, la référence pour acheter des résumés depuis déjà 15 ans

Commencez à vendre!

Récemment vu par vous


$4.49  9x  vendu
  • (0)
Ajouter au panier
Ajouté