User Tools

Site Tools


reference_useful_in_training_situations

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
reference_useful_in_training_situations [2022/07/20 07:57] – Added small vs large teams hansreference_useful_in_training_situations [2022/07/22 08:46] (current) – Add WIP limit video hans
Line 40: Line 40:
   * [[https://assets.thoughtworks.com/articles/adaptive-leadership-accelerating-enterprise-agility-jim-highsmith-thoughtworks.pdf|Adaptive Leadership Accelerating Enterprise Agility]] - Jim Highsmith. Talks about the way we need to bring the agile mindset to the enterprise.   * [[https://assets.thoughtworks.com/articles/adaptive-leadership-accelerating-enterprise-agility-jim-highsmith-thoughtworks.pdf|Adaptive Leadership Accelerating Enterprise Agility]] - Jim Highsmith. Talks about the way we need to bring the agile mindset to the enterprise.
   * [[http://web.efzg.hr/repec/pdf/Clanak%2013-09.pdf|Work Characteristics and Work Performance of Knoweldge Workers: What Goes Hand in Hand?]] - Research paper on knowledge work and importance of various characteristics of the work on the performance of knowledge workers. From abstract "The aim of the paper was to investigate the interplay among a wide range of work characteristics and knowledge workers’ performance outcomes. Specifically, we examined the nature of relationships between various task-, knowledge- and social characteristics of work design and both task and contextual performance. Using an adapted Work Design Questionnaire and applying PLS-SEM modelling technique, we analysed cross-sectional and cross-occupational sample of 512 Croatian knowledge workers from 48 organizations. Our findings confirmed the existence and importance of interaction between work characteristics and work outcomes. However, the results suggest that only knowledge characteristics of work design exhibit a significant effect on both distinct dimensions of work behaviour, while task and social characteristics showed different effects on task and contextual performance, respectively."   * [[http://web.efzg.hr/repec/pdf/Clanak%2013-09.pdf|Work Characteristics and Work Performance of Knoweldge Workers: What Goes Hand in Hand?]] - Research paper on knowledge work and importance of various characteristics of the work on the performance of knowledge workers. From abstract "The aim of the paper was to investigate the interplay among a wide range of work characteristics and knowledge workers’ performance outcomes. Specifically, we examined the nature of relationships between various task-, knowledge- and social characteristics of work design and both task and contextual performance. Using an adapted Work Design Questionnaire and applying PLS-SEM modelling technique, we analysed cross-sectional and cross-occupational sample of 512 Croatian knowledge workers from 48 organizations. Our findings confirmed the existence and importance of interaction between work characteristics and work outcomes. However, the results suggest that only knowledge characteristics of work design exhibit a significant effect on both distinct dimensions of work behaviour, while task and social characteristics showed different effects on task and contextual performance, respectively."
 +  * [[https://www.youtube.com/watch?v=W92wG-HW8gg|WIP: why limiting work in progress makes sense (Kanban)]] - Good illustration of the use of WIP limit to optimize both number of customers served (business benefit) and time to service each customer (customer benefit)
   * [[https://www.qsm.com/risk_02.html|QSM Study on Effectiveness of Small Teams vs Large Teams]] - presented in the context of "adding team members late in the project" but also captures specific case comparing result on schedule and cost of work with teams <= 5 vs teams >= 20. Result is that you get little schedule compression with large teams, but this is at massive change in cost (5 people vs 20 people). Their conclusion is that it perhaps has something to do with the amount of defects produced - much more from large teams.   * [[https://www.qsm.com/risk_02.html|QSM Study on Effectiveness of Small Teams vs Large Teams]] - presented in the context of "adding team members late in the project" but also captures specific case comparing result on schedule and cost of work with teams <= 5 vs teams >= 20. Result is that you get little schedule compression with large teams, but this is at massive change in cost (5 people vs 20 people). Their conclusion is that it perhaps has something to do with the amount of defects produced - much more from large teams.
   * [[http://projectcartoon.com|Create your own project cartoon]] - remember that picture - what customer asked for, what project management understood, etc. Here you can create your own.   * [[http://projectcartoon.com|Create your own project cartoon]] - remember that picture - what customer asked for, what project management understood, etc. Here you can create your own.
   * [[http://www.mountaingoatsoftware.com/blog/sliding-toward-success|Article - Sliding Toward Success]] and related tool [[http://www.mountaingoatsoftware.com/tools/project-success|Project Success Sliders Tool]] - Mike Cohn's approach to working trade-offs between the various constraints on a project.   * [[http://www.mountaingoatsoftware.com/blog/sliding-toward-success|Article - Sliding Toward Success]] and related tool [[http://www.mountaingoatsoftware.com/tools/project-success|Project Success Sliders Tool]] - Mike Cohn's approach to working trade-offs between the various constraints on a project.
   * [[http://www.thisamericanlife.org/radio-archives/episode/561/transcript|This American Life - NUMMI]] and how America is slowly learning the lean lesson from Toyota.   * [[http://www.thisamericanlife.org/radio-archives/episode/561/transcript|This American Life - NUMMI]] and how America is slowly learning the lean lesson from Toyota.
 +  * [[https://www.youtube.com/watch?v=Zs3ML5ZJ_QY|Systems Thinking in a Digital World - Peter Senge]] - the title says it all. Pete is the author of "The Fifth Discipline".
   * [[https://www.rallydev.com/content-request?nid=6546|Software Development Performance Index]]. My copy {{:whitepaper-sdpispecifications-v1.pdf|}}. This is work that came originally from Larry Maccherone while working with Rally. Ideas is to use performance, quality (release ability), predictability, and responsiveness. For example:   * [[https://www.rallydev.com/content-request?nid=6546|Software Development Performance Index]]. My copy {{:whitepaper-sdpispecifications-v1.pdf|}}. This is work that came originally from Larry Maccherone while working with Rally. Ideas is to use performance, quality (release ability), predictability, and responsiveness. For example:
     * Release ability - if team worked on nothing else but close out bugs how long     * Release ability - if team worked on nothing else but close out bugs how long
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/reference_useful_in_training_situations.1658329038.txt.gz · Last modified: 2022/07/20 07:57 by hans