IETF's 2025 April Fool's gag.

Daily stand-ups are a classic example of learned helplessness. We all know they’re useless, but we tell ourselves “that’s just how things are” and do nothing...

Today’s guest post is from Grace Thomas, Senior Digital Collections Specialist on the Library of Congress Web Archiving Team. You can read more about the Web Archiving Team right here on the Signal. In the web archiving community, we build the plane and fly it simultaneously. While this pattern is present in most disciplines, web […]

The De-risking Government Technology Project provides expert, actionable guidance to the public sector for delivering federally-funded, custom technology projects successfully.

This is RonJeffries.com, the combination of new articles, XProgramming, SameElephant,  and perhaps even some new items never before contemplated.  Copyright © 1998-forever Ronald E Jeffries

They couldn't get any women to go. GOSH WHYEVER NOT. (Good in-class exercise for 500.)

A software development methodology has created more than just code

Plays are free workshop resources for addressing common team challenges and starting important conversations.

[Speaking points for: http://tinyurl.com/hf3p8pw] Commonly used in software development, Scrum is a simple and practical project management methodology. This p…

This article describes a case study in which a small team from the digital initiatives group and metadata services department at the University of Colorado Boulder (CU-Boulder) Libraries conducted a pilot of the Scrum project management framework. The pilot team organized digital initiatives work into short, fixed intervals called sprints—a key component of Scrum. Over a year of working in the modified framework yielded significant improvements to digital collection work, including increased production of digital objects and surrogate records, accelerated publication of digital collections, and an increase in the number of concurrent projects. Adoption of sprints has improved communication and cooperation among participants, reinforced teamwork, and enhanced their ability to adapt to shifting priorities.

Stuart Wray wrote a paper analysing how pair programming actually works in team environments and identifies four mechanisms that can be applied to improve the effectiveness of pair programming, and why it results in better quality products.

User stories are one sentence user narratives with a specific syntax that drives thoughtful, collaborative, adaptive product development.