Home
Rick Cogley's Library tagged → View Popular
blog:Cogley - Large Project Inequities
The thought that "no correctly-spec'ed project gets approved" leads me to lots of questions, and no real answers this morning.
I was thinking about the massive projects that the world has seen, like the Pyramids, great Dams, Bridges, Skyscrapers and Railways, or well-designed and -architected cities in general, and wondering: Are these things we marvel at, built on great inequities? Inequities that people of certain demographics cannot even imagine (thinking about myself as a white, male, middle-class American).
It's not comfortable to think about, but would such marvels even exist if there were not the exploited and the exploiters? Can this said to have been even necessary for technical progress?
blog:Cogley - Bus tours give insight into Japan PM
A friend mentioned that she understands better "why Japanese are like they are", after having been on a weekend bus tour to Mt. Fuji. I've been on Japanese bus tours before, but it never really dawned on me that they could be a window on the soul of the Japanese, but I suppose they are, in a way. I've always been against them, but occasionally bow to pressure from the higher authorities at my house, like my wife and daughters, and go on a bus tour.
blog:Cogley - Guerilla Collaboration
Aaron Fulkerson, the CEO at Mindtouch - makers of the awesome mashable wiki "Deki" - writes about the state of collaboration in his post Three Decades Later. Revolt Or Die.
As Aaron mentions, the current state of affairs with regard to collaboration is very much email centric. However, email is terrible for collaboration. If you have never given this much though, sit a moment and really think through what it means to try to manage a project, with file versioning, in email. If you think on it, you can see how easily email can snowball out of hand, with noone on the team knowing what file or which piece of info is the current, latest version.
I know this from painful experience. We have had to manage very large projects via email, because of the strong resistance at the client to any web-based applications. People have been adamant: "we use email for everything." Yikes. There are even project management applications that cater (pander?) to this attitude, like Wrike.
blog:Cogley - Guerilla Collaboration
Aaron Fulkerson, the CEO at Mindtouch - makers of the awesome mashable wiki "Deki" - writes about the state of collaboration in his post Three Decades Later. Revolt Or Die.
As Aaron mentions, the current state of affairs with regard to collaboration is very much email centric. However, email is terrible for collaboration. If you have never given this much though, sit a moment and really think through what it means to try to manage a project, with file versioning, in email. If you think on it, you can see how easily email can snowball out of hand, with noone on the team knowing what file or which piece of info is the current, latest version.
I know this from painful experience. We have had to manage very large projects via email, because of the strong resistance at the client to any web-based applications. People have been adamant: "we use email for everything." Yikes. There are even project management applications that cater (pander?) to this attitude, like Wrike.
blog:Cogley - How to Backup FriendFeed, Twitter or other RSS Feeds -- Rick Cogley
How to Backup FriendFeed, Twitter or other RSS Feeds -- Rick Cogley | Using a similar technique to my previous post, we can use an RSS-to-email service like FeedBurner to essentially backup RSS feeds via email. This will give you a pretty-good backup to IMAP, or, by using email-to-blog services, a post of your posts.
Here's how I plan to do this...
Article from Rick Cogley - The Principles behind the Agile Manifesto
Looking at the basics of Agile in more detail to help me apply it to general, non-development project management, the principles behind the Agile Manifesto are readily available for us to read and learn from. -- Rick Cogley
blog:Cogley - Agile Principles, Translated, with Some Commentary
To help my Japanese colleagues understand the concepts of Agile more easily, after the jump, I'll translate the principles into Japanese, under the original English from the Agile website. The Japanese translations and any mistakes therein are solely my responsibility. Further, I'll take the opportunity to comment on what I see as important in the principles. For instance, do the principles allow for or even demand a lazy, free-for-all approach? Can an inexperienced team do Agile effectively, or, is mentoring needed?
Selected Tags
Related Tags
Sponsored Links
Highlighter, Sticky notes, Tagging, Groups and Network: integrated suite dramatically boosting research productivity. Learn more »
Join Diigo