| General > General Technical Chat |
| New Project Fears. |
| << < (2/2) |
| Tomorokoshi:
Think back through the various books on projects and project management you have read or slogged through over the years. Between those and your experience with previous projects you may be able to guess at what the next few months will be like. Anyway, without a requirements document, in a sense you are now able to help chart part of the path. Some of the questions you could have ready: 1. Who will be responsible for the build? Nightly build? 2. What is being used for source control? 3. What is the scope / scale / size of the Java program? 4. What is the scope / scale / size of the database it works with? 5. Any specific technologies that are involved? Database, etc. 6. Is there a manual for the existing program? 7. What methodology will be used? Agile? Phase-Gate? Random Hacking? 8. As relevant: Who is the Scrum Master? Project Manager? 9. Which service provider will host the new application? 10. How many active users at once? 11. Will there be an iPhone / Android app? |
| paulca:
Had a few calls with my work peers in my company and feel a bit better now. On anxiety, I get paid a load of money to do stuff. When I am not doing stuff I feel anxious. If I have a day where I work flat out and actually deliver value I log off happy and feel safe in my job. Spending what must be 4 weeks now idle makes me very nervous. Currently I'm trying to work out the playing field. This unnamed company of course rename or rebrand their components and a lot of them are *aaS - "whatever as a service", thus managed with complex access request chains etc. Pain in the ass TBH. Why can't they call a spade a spade? It does seem, like in all banks, nothing is likely to happen fast, so much bureaucracy and dozens of access requests that will take a day to process each tends to slow things down. Hopefully that holds as you can always hide behind their bureaucracy and use it as an excuse :) I'll let you know how it goes. |
| paulca:
So it turns out - as expected - I was over reacting. Kick off with the customer revealed they haven't even decided on the actual requirements yet. But it's basically just a dev ops project to take existing services and move them to containerised cloud images. There are a few easier ones top of the queue before the hard ones and it's a time bound project. Got some access to systems trickling in and I don't think any pressure will ramp up for a while yet. Today I got the first sub project to build, so I'm sitting on that info for tomorrow's update and going to take it easy today. :) |
| Dubbie:
Glad to hear it all worked out well! A lesson for next time! I am not an EE, but in my professional life, one mark of real experience is knowing when to worry and when to not. |
| paulca:
My fear always grows when I end up sitting idle staring at the wall cause I don't know what I'm doing. Why would people pay me lots of money to do that? But today I find myself doing that. I'm a software developer. It usually goes one of two ways. 1. Deployment and release management is simple - development do it, it's basic and 100% open to development customisation. We own it. 2. Deployment and release management is complex and convoluted - There is a team responsible for it. Development create an artefact that ticks their boxes, they deal with the rest. However, this current project it seem I am one of those "Dev Ops" team. Probably sold as a dev ops expert by my company. But their deployment and release management process is incredibly complicated, massively customised, heavily regulated and completely out of my control. It would be all very well learning dev ops and some of the tech I'm facing, but it won't be that. It will be learning my way through all their overly complex processes and policies while wading through a constant swamp of customised terminology and nomeclure. There are no spades called "Spade" in this place. Somehow I have to FGH my OKJ with a G4F5 from the AIM on the GIUY repo, having applied for a 55FTR from QQES so I can use a YYU pipeline. You get that? No. Nor did I. |
| Navigation |
| Message Index |
| Previous page |