Search

Snapchat started in 2011 as a place where users could communicate through photo, video, and text messaging that would disappear once viewed. It was very much a closed network platform [...]

In a large organization, informal communication and simple backlogs are not sufficient for the management of requirements and development work. Many large organizations are struggling to successfully adopt agile methods, but there is still little scientific knowledge on requirements management in large-scale agile development organizations. We present an in-depth study of an Ericsson telecommunications node development organization which employs a large scale agile method to develop telecommunications system software. We describe how the requirements flow from strategy to release, and related benefits and problems. Data was collected by 43 interviews, which were analyzed qualitatively. The requirements management was done in three different processes, each of which had a different process model, purpose and planning horizon. The release project management process was plan-driven, feature development process was continuous and implementation management process was agile. The perceived benefits included reduced development lead time, increased flexibility, increased planning efficiency, increased developer motivation and improved communication effectiveness. The recognized problems included difficulties in balancing planning effort, overcommitment, insufficient understanding of the development team autonomy, defining the product owner role, balancing team specialization, organizing system-level work and growing technical debt. The study indicates that agile development methods can be successfully employed in organizations where the higher level planning processes are not agile. Combining agile methods with a flexible feature development process can bring many benefits, but large-scale software development seems to require specialist roles and significant coordination effort. [ABSTRACT FROM AUTHOR]

Providing open access to digitised collections may be increasingly common, but the UK's flagship museums continue to assert copyright on images of artworks in the public domain. This stymies creativity [...]

Developing a Mobile Application for Electrochemiluminescent Biosensor Control and Analysis. Jonathan Swerdlow, Rodney Summerscales and Hyun Kwon, Andrews University Using a mobile device such as a smartphone for initiating and [...]

JOURNAL OF THE NEW MEDIA CAUCUS v. 9, no. 1 (Spring 2013): Special issue: 'Tracing New/Media/Feminisms.' Issue editor: Stephanie Tripp. Publisher: New Media Caucus. ISSN: 1942-017X. Free electronic access at [...]

This article proposes an approach for improving the software process of a small/medium company. The methodology is presented through a case study during which estimation models have been applied, evaluated and introduced in a telecommunication software development process. The proposed methodology uses Bayesian Belief Networks to represent the relationships among implementation, product and process metrics and their impact on the development effort. The estimation models that were derived were applied and evaluated on the on-going projects of the company. Finally, by performing the same analysis on data from the International Software Benchmarking Standards Group (ISBSG) repository, it is demonstrated how one company can utilize data from other companies when it lacks sufficient data of its own. Copyright © 2009 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]