Today I tried @hjarche's advice and started my search on Twitter. My search term was "project management for artists." I found a lot of depressing stuff, implying that all artists should use Waterfall methods of project management. My resolve is firm to instead teach an Agile technique at my talk tonight. I'm going to focus on Kanban.
This is the argument I have with my husband. He thinks the future will be unmitigated hell, a free-for-all with weapons and scarce resources. My future is based on a continuing reduction in injustice.
I think the next such revolution, likely sometime in the twenty-first century, will challenge the economic implications of the nation-state. It will focus on the injustice that follows from the fact that, entirely by chance, some are born in poor countries and others in rich countries. (Source)
@hjarche says you should "ensure that over 50% of your probes fail." There's a lot of Agile here. The goal for me is to begin identifying probes. Here are some that I am already doing:
- Getting set up in the Expert's Corner at the Hannah Grimes Center
- Giving a free talk (tonight!) on Project Management for Artists and Makers
How to launch a Probe, such as a community of practice:
- What are you testing?
- How will you know if you have made progress?
- What is the smallest probe we can do?
- Measure the results.
- Do it again, and again, with slight variations as needed.
- Measure the results and either amplify it or stop doing it.
But after a good start, my day goes to heck. Had two good conversations with folks in my network, including some good ideas (AP says, when you send off an informal proposal of some sort, include the words "I'll check in with you in a week if I haven't heard from you"), but then I devolve to RSS and Twitter and yes, PKM.
At 3 PM, I turn it around and head into a few Pomodoros on the project management for artists workshop that I'm running on Thursday. I'll start by mind-mapping all my ideas.
Luckily, that exercise went really well. It's interesting thinking about how to translate Agile Project Management into words that will be relevant to artists and makers. I've pretty much decided to focus on Kanban as a tool for them, and emphasize the importance of limiting Work In Progress (WIP).
I'm fascinated about the way we're no longer putting up with BS at work. In Agile, we talk about the HIPPO (the Highest Paid Person's Opinion). In the old days, whatever the HIPPO was, that's what we did. Now we just call it the HIPPO and keep working on figuring out what we should really do.
FOG- Fact , opinion or guess. Play that game anytime anybody says anything in a meeting.
A fact is something independently verifiable. An opinion is a statement about the fact. A guess is a prediction of a fact.
My working out loud day begins with a few minutes planning the day. I set up the new day in my Bullet Journal with the meetings I have scheduled and the one or two things that I know I absolutely have to do today.
I then check my Liquid Planner project management software, as this has my big running list of all the things on my plate. I may add one or two more items to the Bullet Journal at this point in the morning, but I try to keep the Journal focused on the few things that I have to get done. Once those are complete, then I can go back to Liquid Planner to pull a few more items off the big list.
I like Liquid Planner because it allows me to estimate how long I think a task will take. I then use its scheduling engine to help prevent me from over-scheduling any given week. It mostly works as a strategy ...
It seems to me that all of sudden people are talking about guaranteed minimum income and disconnecting income from work. The idea being that we work to fulfill our goals, while money comes from other sources. I can't quite imagine how it can work, but the ideas intrigue me. In a world where we see individuals devote thousands of hours to Open Source development without remuneration, it seems that we have proven that humans are not lazy idiots who would just watch TV all day if you let them. OK, at least that some humans are not lazy idiots.
The human rental today manifests itself as the voluntary exchange of personal labor for a salary or wage. A legitimate arrangement requires workplace democracy and worker ownership whenever human labor is involved.
Related to: (Source)
In a workable future —Harold Jarche | sense-making for the connected workplace
thank you to @hjarche for this pointer:
I want to link this report to the web site I found recently about Ending Temporary Slavery ... actually it's Abolish Human Rentals
Here's the link to the PDF of the Workable Future report:http://www.iftf.org/future-now/article-detail/10-strategies-for-a-workable-future/
I chose #NoEstimates as my PKM community topic because I wanted to learn more about this project management philosophy. I've been a project manager for 20 years, and have prided myself on my own estimation abilities as well as my teaching skills in this area. At the same time, I have personal experience that tells me that we often over do it with estimation, as though we actually were able to predict the future (if we could do that, let's all go play the horse races instead).
Thus, I'm open to the ideas of #NoEstimates. But in the 48 hours I've spent with the #NE folks on Twitter, the first thing I noticed is the vitriol of those who oppose No Estimates. It's fascinating! I intend to keep watching and try to understand both sides.
@henebb Going on NEers in my mentions today, practicing NE seems to mostly entail shallow mocking memes & zero substance. @richardthefrank
I think this is relevant to Personal Knowledge Management. I've already had the experience of saving too much information in my Evernote. Yes, it's searchable, but I am quickly inundated and overwhelmed by the amount of information that I have in certain topics. How do I build a repository that somehow never gets stale? And what have I saved that I'd want to protect -- though I've tried to be careful about that?
(In addition, it is totally cool that I was able to copy this card from rainystreets.wikity.cc rainystreets.wikity.cc with the click of a button)
All this makes data a toxic asset, and it continues to be toxic as long as it sits in a company's computers and networks. The data is vulnerable, and the company is vulnerable. It's vulnerable to hackers and governments. It's vulnerable to employee error. And when there's a toxic data spill, millions of people can be affected. The 2015 Anthem Health data breach affected 80 million people. The 2013 Target Corp. breach affected 110 million. This toxic data can sit in organizational databases for a long time. Some of the stolen Office of Personnel Management data was decades old. Do you have any idea which companies still have your earliest e-mails, or your earliest posts on that now-defunct social network? (Source)