Re: Completely new to Agile Dev principles, and it sure feels like I'm in over my head right now...
"Michael Wollin [email protected] [SCRUMDEVELOPMENT]" <[email protected]> Thu, 21 Sep 2017 12:43:34 -0400
| Newsgroups | gmane.comp.programming.scrum.general |
|---|---|
| Message-ID | <[email protected]> |
Agree. Mike’s advice is spot on! > On Sep 20, 2017, at 7:14 PM, Scott Griffin [email protected] [SCRUMDEVELOPMENT] <[email protected]> wrote: > > > Mike, > > Actually, that was probably the best thing I could have heard right now. Me running around with my hair on fire isn't going to put the inferno out, it's just going to make me look as incompetent as everyone else. > > Thank you, sir. > > > On Wednesday, September 20, 2017 5:58 PM, "Michael Vizdos [email protected] <mailto:[email protected]> [SCRUMDEVELOPMENT]" <[email protected] <mailto:[email protected]>> wrote: > > > > If you have one boss, talk to that person about what is keeping them up at night that you can help solve for them. > One. Thing. > Work on that. > The rest is burning and will continue to burn. > While it totally can be a career limiting move (as you have stated with the resume comment) remember your job is to WHAT (get clarity on that). > I am sure others will have comments coming. > Good luck with this. I feel deep empathy for you. > Agile and Scrum exposes organizational dysfunctions. Here they are. > - Mike Vizdos > Focus. #deliver > > On Wed, Sep 20, 2017, 4:29 PM [email protected] <mailto:[email protected]> [SCRUMDEVELOPMENT] <[email protected] <mailto:[email protected]>> wrote: > > Hi, Scott here. I work remotely (strike 1 against Agile Dev) as a newly christened Project Manager for a software company that uses a combination of onsite and offshore assets (strike 2) in their workflow as a matter of process. > > The project I was handed as my first effort in this role is an enormous (strike 3) database migration, where the client insisted we employ Agile Dev principles because they wanted tangible deliverables to be delivered regularly (which would be reasonable if not for the scope of the project). > > I knew, when I saw the scope of this project, that Agile was not going to work, so I've been doing my best to adapt at least some of the principles to improve workflow and engagement. > > So now I'm neck-deep in it, and I'm taking fire from all directions. Trying to teach the offshore team about Agile principles and my need for them to be creatively involved in the project instead of just waiting for me to tell them exactly what to do and how to do it is an exercise in futility thanks to language and culture barriers. Even the client side is driving me nuts. The communication is so poor, my primary contact on the client side is telling me that my burndown chart tells him that my team is falling behind because the actual tickets remaining line is below the projected line (!!!!!) > > I'm at my wit's end here. Advise would be great. And yes, I know, send out resumes is good advice, but that's really not an option at this point. I have to figure out how to keep this whole thing from crashing and burning. > -- > Thank you. > - mike > Focus. #deliver > www.michaelvizdos.com <http://www.michaelvizdos.com/> > > > > >