Comment #2: Krzesimir
|
Hello Krzesimir, This is a well-written post which also makes the topic at hand interesting to read about. It sounds like you and your team have found a good system for your work, especially in regards to your size. The success in the logistical work involved in constructing this system would presumably be of your responsibility as producer and scrum master, as well as your education in the project management minor, which reflects quite well on you and your quality of work. Cross-disciplinary knowledge is even more important in a small team, as you have mentioned. A good visualization of this is a T-shaped diagram, with the top of the T being the different disciplines and the “leg” of the T being a specialization. A T-shape is considered ideal as it represents the person in question having at least a little bit of knowledge in every part of the item at hand, e.g. a project or company, while also having more advanced skill in their target area. Presence in group work is also a great benefit you bring up in your post. It allows for open communication and more effective collaboration. It would have been nice to know a little about your process in establishing your group’s work structure. Many teams have problems with coordinating schedules or having each individual cooperate. From my own experience, this is easier in a smaller group like yours. If there was little problem involved then I can understand why you may not consider writing it in your post. Overall, great job. It is difficult to think of worthy criticisms to be made of your post. One thing is that I do not see an image in the post, which I believe to be a requirement. Although, I do remember something to the tune of “if it is relevant” being said about that. So I am unsure. Anders [Kemppainen] https://krzesimirsite.wordpress.com/2018/02/15/working-in-a-small-team/  |