Open jleo3 opened 11 years ago
Are you going to share this with general public? Happy Easter and see you Tomorrow!
Thanks,
Sent from my mobile device. Please excuse any errors.
On Mar 31, 2013, at 1:09 PM, Joe Leo notifications@github.com wrote:
Really wishing I would have listened to @arielvalentin when he told me to blog about my agile workspace organization. Would come in handy.
@jleo3 "better late than never" GET ON IT!!!
So here we are. When I was a Cyrus Innovation employee consulting at Boeing, I enjoyed my best experience in an agile workspace. We had (and I think the current crop of Boeing developers still have) immaculate agile swimlanes, insightful information radiators, and comfortable pairing stations. The sense of organization and clarity spread to the teams' psyche. We held standups, kaizens, and planning sessions at regular times and we rotated the many non-coding responsibilities every agile team must share through each member of the team. It was beautiful.
For me, that was a long time ago. I'm two jobs removed from Cyrus and seven months into my latest gig. I've joined a successful, close, and hardworking team and I'd like to think I've helped continue this success.
But we could be even better. We could always be better. And lately I've come to think that part of this means getting back to my roots of agile organization.
I'm going to start with the practices that I apply every day, those that I do out of habit and without thinking. It's worth a closer look at those, if only to reinforce why I'm doing them. But I'm going to quickly move into areas where I'm trying new experiments with this relatively new team to see what sticks and what makes us better.
— Reply to this email directly or view it on GitHub.
Of course I am! Actually, I wanted to write a couple more posts so I could get ahead of the curve before releasing them, but that point may be moot if I'm putting all my ideas in a public space!
I am coming up tomorrow morning, so don't party too hard tonight and I'll see you bright and early!
I will be hitting the pool tonight then in bed early.
Thanks,
Sent from my mobile device. Please excuse any errors.
On Apr 1, 2013, at 3:41 PM, Joe Leo notifications@github.com wrote:
Of course I am! Actually, I wanted to write a couple more posts so I could get ahead of the curve before releasing them, but that point may be moot if I'm putting all my ideas in a public space!
I am coming up tomorrow morning, so don't party too hard tonight and I'll see you bright and early!
— Reply to this email directly or view it on GitHub.
Really wishing I would have listened to @arielvalentin when he told me to blog about my agile workspace organization. Would come in handy.
@jleo3 "better late than never" GET ON IT!!!
So here we are. When I was a Cyrus Innovation employee consulting at Boeing, I enjoyed my best experience in an agile workspace. We had (and I think the current crop of Boeing developers still have) immaculate agile swimlanes, insightful information radiators, and comfortable pairing stations. The sense of organization and clarity spread to the teams' psyche. We held standups, kaizens, and planning sessions at regular times and we rotated the many non-coding responsibilities every agile team must share through each member of the team. It was beautiful.
For me, that was a long time ago. I'm two jobs removed from Cyrus and seven months into my latest gig. I've joined a successful, close, and hardworking team and I'd like to think I've helped continue this success.
But we could be even better. We could always be better. And lately I've come to think that part of this means getting back to my roots of agile organization.
I'm going to start with the practices that I apply every day, those that I do out of habit and without thinking. It's worth a closer look at those, if only to reinforce why I'm doing them. But I'm going to quickly move into areas where I'm trying new experiments with this relatively new team to see what sticks and what makes us better.