COLUMN: Careers
Devrel, the career created for a developer-centric world
By Jennifer Reif, January 2022
Articles Tagged: Project and people management
Articles & Features
Finding the team where you'll grow the fastest
By Jason Benn, July 2019
SECTION: Features
Why digital systems do not reach their full potential in organizations
The continuous evolution of digital systems shaping the workplace and the optimizing of work processes is revolutionary. But despite decades of accumulated experience, there are still plenty of projects that fail completely or deliver unexpected and unacceptable results. This article discusses why problems with the digitalization of working life persist.
By Bent Sandblad, Thomas Lind, January 2019
Running an alt.business: being a good cause and doing good business
Hacker, maker, and engineer Limor "Ladyada" Fried shares her insights on open technologies and business models.
By Limor Fried, June 2017
SECTION: Feature: Augmenting people
Don't replace people. Augment them.
If we let machines put us out of work, it will be because of a failure of imagination and the will to make a better future!
By Tim O'Reilly, December 2016
SECTION: Feature: Designing the workplace of the future
Algorithmic bosses, robotic colleagues: toward human-centered algorithmic workplaces
We already know algorithms can make our lives and our work more efficient, but how can we go beyond that to create trustworthy, fair, and enjoyable workplaces in which workers can find meaning and continuously learn?
By Min Kyung Lee, December 2016
Building a brighter future for crowd work
Skill ladders may help crowd workers to "skill up" as they work. But what other technical innovations will lead to better opportunities for crowd work?
By Jeff Bigham, Kristin Williams, December 2016
SECTION: Features
Making tech more inclusive
Exposing the driving causes behind the lack of diversity in our communities, and how to use your privilege for good.
By Erin Carson, June 2014
Want a tenure?
Why running a startup is a lot like building a research lab.
By Eldar Sadikov, Montse Medina, June 2012
Don't change a thing
As a student of computer science, there's a significant chance you will end up working in software development after graduation. Despite whether your career path takes you into industry or academia, you're likely to have some kind of interaction with software development companies or organizations, if only in trying to get the most out of a project or collaboration.
By Michael DiBernardo, September 2009
Introduction
By Justin Solomon, June 2009
A computer scientist's introductory guide to business process management (BPM)
Computers play an integral part in designing, modelling, optimising and managing business processes within and across companies. While Business Process Management (BPM), Workflow Management (WfM) and Business Process Reengineering (BPR) have been IT-related disciplines with a history of about three decades, there is still a lack of publications clarifying definitions and scope of basic BPM terminologies like business process, BPM versus WfM, workflow, BPR, etc. Such a myriad of similar-sounding terminologies can be overwhelming for computer scientists and computer science students who may wish to venture into this area of research. This guide aims to address this gap by providing a high level overview of the key concepts, rationale, features and the developments of BPM.
By Ryan K. L. Ko, June 2009
Planning and improvisation in software processes
This paper presents the results of an empirical study aimed at examining the extent to which software engineers follow a software process and the extent to which they improvise during the process. Our subjects tended to classify processes into two groups. In the first group are the processes that are formal, strict, and well-documented. In the second group are the processes that are informal and not well-structured. The classification has similar characteristics to the model proposed by Truex, Baskerville, and Travis [12]. Our first group is similar to their methodical classification, and our second group is similar to their amethodical classification. Interestingly, software engineers using a process in the second group stated that they were not using a process. We believe that software engineers who think that they are not using a process, because they have the prevalent concept of process as something methodical that is strict and structured, actually are using an informal (amethodical) process. We also found that software engineers improvise while using both types of processes in order to overcome shortcomings in the planned path which arose due to unexpected situations. This finding leads us to conclude that amethodical processes are processes too.
By Rosalva E. Gallardo-Valencia, Susan Elliott Sim, December 2007
The student's guide to GDC
By James Stewart, December 2007
Observations on teamwork strategies in the ACM international collegiate programming contest
By Saman Amirpour Amraii, December 2007
TigerEvents
By Chris Jordan, Oliver Baltzer, Sean Smith, August 2006
The many dimensions of the software process
By Sebastián Tyrrell, June 2000
Book review
By Kim Moorman, March 1999
Objective viewpoint
By George Crawford, March 1999