I've always liked the idea of a team wiki that functioned at a higher level than one particular project. For example, perhaps I could write an article that breaks down a common pitfall we always run into or tips for improving productivity while using a particular tool. I remember pitching Confluence at one point, too.
The open working area concept isn't my cup of tea. I understand the appeal of that for some, but I enjoy the relative privacy of my cube fort. Personally, I feel that our team manages to communicate freely enough despite the chest-high walls which separate us.
One thing we are trying to strive for more of is the interactive demo like you mentioned in point two. Since our sprints most often don't end with a code deployment, we hope that instead of a deliverable product we can present our accomplished work. Not only do we get to feel like we're "delivering" something but everyone on the team or involved in the project can see the progress we're making.
We have a team wiki that we could be better about being updated. We've do internal presentations that everyone benefits from. But I don't think people are always psyched about carving the time to prepare these.
I'd love to get into mob programming a bit. It's like pair programming, but the code is projected and the whole room drives.
Kim Arnett [she/her] leads the mobile team at Deque Systems, bringing expertise in iOS development and a strong focus on accessibility, user experience, and team dynamics.
Well the idea is that the person typing does not drive, mostly takes instructions, and everyone else collaborates on the solution. Still would be a bit nerve-racking but mostly on a "do I know all the proper keyboard shortcuts" kind of way.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've always liked the idea of a team wiki that functioned at a higher level than one particular project. For example, perhaps I could write an article that breaks down a common pitfall we always run into or tips for improving productivity while using a particular tool. I remember pitching Confluence at one point, too.
The open working area concept isn't my cup of tea. I understand the appeal of that for some, but I enjoy the relative privacy of my cube fort. Personally, I feel that our team manages to communicate freely enough despite the chest-high walls which separate us.
One thing we are trying to strive for more of is the interactive demo like you mentioned in point two. Since our sprints most often don't end with a code deployment, we hope that instead of a deliverable product we can present our accomplished work. Not only do we get to feel like we're "delivering" something but everyone on the team or involved in the project can see the progress we're making.
We have a team wiki that we could be better about being updated. We've do internal presentations that everyone benefits from. But I don't think people are always psyched about carving the time to prepare these.
I'd love to get into mob programming a bit. It's like pair programming, but the code is projected and the whole room drives.
I'd be interested in trying it, but my anxiety would die if I had to code in front of a room of people judging me while in front of a giant screen. 😶😶
Well the idea is that the person typing does not drive, mostly takes instructions, and everyone else collaborates on the solution. Still would be a bit nerve-racking but mostly on a "do I know all the proper keyboard shortcuts" kind of way.