System Thinking insists that systems (of all kinds) must be analyzed as a whole in order to understand its emergent properties and the interrelatedness of its constituent parts (McDermott & O'Connor, 1997). Action Research is a research methodology that lay emphasis on researchers to work with practitioners rather than on them. The modern workplace requires systems thinking because it’s a complex whole that exhibits emergence and it is also in urgent need of expert guidance and knowledge that enables its inhabitants to become more productive and efficient. In the light of the bare minimum of options present for such possibilities, the author makes the case that action research can both teach and enable practitioners to incorporate systems thinking in their workplace. The paper gives a brief introduction to systems thinking and action research then makes the case for action research in the workplace and finally rounds off with strategies for conducting successfully action research.
We are tired of XP, Scrum, Kanban, Waterfall, Software Craftsmanship (aka XP-Lite) and anything else getting in the way of...Programming, Motherfucker.
We are tired of being told we're autistic idiots who need to be manipulated to work in a Forced Pair Programming chain gang without any time to be creative because none of the 10 managers on the project can do...Programming, Motherfucker.
Europäische Geschichte Online (EGO) is an online European transcultural history composed of multimedia knowledge items encompassing the period from 1450 to 1950. EGO is methodologically pragmatic, international and interdisciplinary. It combines a variety of approaches and perspectives from debates in multiple languages and thus interlinks international scholars working in the various disciplines of European history.
IceScrum is an J2EE application for using Scrum while keeping the spirit of a collaborative workspace. It also offers virtual boards with post-its for sprint backlog, product backlog and others.
The tool offers everything that is in Scrum :
*
The role management: Product Owner, ScrumMaster, Team member and StakeHolder
*
The product backlog management with advanced features for prioritizing stories
*
Scrum lifecycle including a roadmap view
*
Release planning
*
Sprint backlog, as a task board facilitating the Scrum ceremonial
*
Management of impediments
*
Chart production such as burndown charts, velocity charts, cumulative flow diagram
Icescrum offers others agile practices like :
* Roadmap
* Vision
* Features
* User stories
* Acceptance tests associated to stories
* User roles
* Planning poker
WebSM website is dedicated to the methodological issues of Web surveys, but it also covers the broader area of modern technologies and survey data collection. It provides latest news and a database on literature, software, events, and people. WebSM site was funded by the European Union in 2003-2005.
Recent functional neuroimaging studies have shown that reflecting on representations of the present self versus temporally distant selves is associate...
However I don't think this is the key point about agile
methods. Lack of documentation is a symptom of two much deeper
differences:
Agile methods are adaptive rather than predictive.
Engineering methods tend to try to plan out a large part of the software
process in great detail for a long span of time, this works well until
things change. So their nature is to resist change. The agile methods,
however, welcome change. They try to be processes that adapt and
thrive on change, even to the point of changing themselves.
Agile methods are people-oriented rather than
process-oriented. The goal of engineering methods is to define a
process that will work well whoever happens to be using it. Agile
methods assert that no process will ever make up the skill of the
development team, so the role of a process is to support the
development team in their work.In the following sections I'll explore these differences in
more detail, so that you can understand what an adaptive and
people-centered process is like, its benefits and drawbacks, and
whether it's something you should use: either as a developer or
customer of software.