The old asterisk voice menu system I used to run was pretty good at shutting down telemarketers and robocallers while still letting legitimate callers through. I don't think it'd be so easy to implement on an android phone, although it really should be. Maybe that phone Canonical is working on will have more open standards, but I'm not holding my breath.
They let it run a little too long this time, though. Hybrids and electrics have had a chance to get a foothold in the market, and some people are already starting to think about how pure electric vehicles and ones with fuel cells could potentially change how electric grids work. It wouldn't take a very big push for countries to start adopting electric vehicles powered with Clean Atomic Energy. And that'll plunge us into the next ice age lickety split, once global warming starts to reverse. Hah, didn't see THAT coming, did you?
Were there any tasks that only one person could have achieved? Very few, really. There was some work around making the code more stable that I ended up doing. That involved changing how the code was launched, building the code base with electric fence and using a a debugger to find the locations of core dumps. I feel like that's stuff any programmer can do, but the rest of the team didn't seem to have any experience with that process. But agile is also willing to accept a half-assed job if a half-assed job meets the needs of the business. It really doesn't matter to agile if someone on the team gets pulled in every weekend because the program can't run without constant hand-holding, as long as the business' needs are being met.