Scott Griffin griffin8r73@yahoo.com [SCRUMDEVELOPMENT]
2017-09-28 03:58:18 UTC
Well...Â
I finally was able to pin my boss down tonight and really dig into the concerns that I had about the team, the situation, and my frustrations.
It turns out (and this is my lack of expertise in software shining through) that the particular environment we are working in (Azure) and the data models we are trying to implement (tabular) are so new, my team of what would normally be highly competent and very smart people are essentially flying by the seats of their pants, mostly relying on his vast expertise in development and architecture along with daily training sessions (that he didn't even tell me were going on) from other software architects he brought in to improve their competence.
I told him, if I had been aware of this information at the beginning of the project, my stress level never would have gotten this high, because all the concepts I'm trying to present to them (anticipatory thinking, granular object creation, story point bids, etc) are essentially non-functional at this juncture in the project, because they are still trying to get a feel for time investments and report flow and development. Â
But, we are still going to drill on communication. On that we are both agreed. There's just way too much of a disconnect between me and the team in terms of communication, and that has to improve. Â
That said, all of your feedback was certainly instrumental in pulling me back off the ledge, and for that I thank you. I look forward to updating you with more positive news in the future.
I finally was able to pin my boss down tonight and really dig into the concerns that I had about the team, the situation, and my frustrations.
It turns out (and this is my lack of expertise in software shining through) that the particular environment we are working in (Azure) and the data models we are trying to implement (tabular) are so new, my team of what would normally be highly competent and very smart people are essentially flying by the seats of their pants, mostly relying on his vast expertise in development and architecture along with daily training sessions (that he didn't even tell me were going on) from other software architects he brought in to improve their competence.
I told him, if I had been aware of this information at the beginning of the project, my stress level never would have gotten this high, because all the concepts I'm trying to present to them (anticipatory thinking, granular object creation, story point bids, etc) are essentially non-functional at this juncture in the project, because they are still trying to get a feel for time investments and report flow and development. Â
But, we are still going to drill on communication. On that we are both agreed. There's just way too much of a disconnect between me and the team in terms of communication, and that has to improve. Â
That said, all of your feedback was certainly instrumental in pulling me back off the ledge, and for that I thank you. I look forward to updating you with more positive news in the future.