Here we are, again
Jan. 22nd, 2022 08:17 amThis week was busy-busy-busy - it was the week I expected LAST week to be.
The new project is gradually building momentum, not least by changing its title for the third time :D But it was the customer who renamed it, which I'm happy about. Really, it doesn't matter what we call it as long as EVERYONE calls it the same thing. We're experimenting with DevOps for this one, which adds a layer of risk to the whole thing. Firstly, it's a change in working practice for the devs (who are notorious for never writing anything down); secondly, the platform lead for the team that is going to be most involved may not give the wholehearted support that the others will. Part of me wants to get everything set up and say to the team - this is how it is, deal. But I'm a collegiate, work-with-not-against, bring everyone along, kind of person. Thankfully, it's really the PM's headache - I'm just there for support. An added complexity is that said PL's partner is due to have a baby any moment and they're taking a month off. Our general consensus is to wait until they're back because we do want them on board but there's stuff to get on with in the meantime.
There are pockets of use around the department and we have people who've used it in a past life and are real enthusiasts. I think it LOOKS great but big and complicated. In the interests of consistency, and as a way of getting people onboard, I think we should push for some proper training, with this particular project as the driver. So, I suppose we can begin making a business case for that whilst the PL is off, too? There is definitely a case for bringing the former, current and future users together to have a conversation - so far, I've sort of pin-balled around between individuals, which is one of the reasons I've felt I was getting nowhere. What I am keen on going forward is that I'm in a support/facilitation role and not driving the bloody thing!
The other main project I'm working on is moving out of workshopping and into development. And I'm taking over the RAPID log review process (that's a RAID + Principles - we're rather proud of it :D ) as part of my evidence gathering. The expectation is that I'll do the same for the new project. Anyway, it's going to result in the usual fun and games of finding a suitable hour in some very busy diaries *facepalm*
Oh, and I spent some time wresting with the Roadmap. There is stuff in the 'start in the next 6 months' box that has been there for at least a year because it's taken that long to get it into a format we're all happy with - ROFL. But it feels like we're shuffling to that point - and one of those projects is the new one mentioned above, so it might actually be the first thing to come OFF the Roadmap *feels giddy at the thought* And then we can move something in the '12 - 36 month' box up!
One move that seems very positive is we're trying to bundle some of the smaller things that come in via the project request form either into something that's already happening or with some of the other small things, to give us a critical mass of stuff. Again, the first project is an example - 3 pieces of work with a significant overlap of requirements has led to a single project, with the caveat that there's likely to be a pull in at least 2 different directions >D
But it's all good. I'm busy, and busy means employable. And it does feel like we're making the CIO happy - or at least happier!
In non-work, I'm up-to-date with 'Around the World' and 'The Tourist', and the new series of 'The Rookie' started this week. The opening episode was... I dunno - they had to wrap up the cliffhanger they left at the end of the last series, I suppose, but it felt like a LOT of compromises were made. Anyway, that's done, now, so I'll see how the rest goes. Still don't know how they've got 4 series out of a year-long process :D :D
I made some progress with my 70x700 novel, thinking about the central character's potential loss of humanity as a reaction to how everyone else treats them, and what jolts them out of it. Could be interesting - also could disrupt everything I've done so far, but it's all in plan form, which is easier to redo!
And I'm planning to run 8am online Sunday services during Lent with the Rector. I actually miss the online services, so I'm looking forward to it.
And that's all for now - bye for now DW!
The new project is gradually building momentum, not least by changing its title for the third time :D But it was the customer who renamed it, which I'm happy about. Really, it doesn't matter what we call it as long as EVERYONE calls it the same thing. We're experimenting with DevOps for this one, which adds a layer of risk to the whole thing. Firstly, it's a change in working practice for the devs (who are notorious for never writing anything down); secondly, the platform lead for the team that is going to be most involved may not give the wholehearted support that the others will. Part of me wants to get everything set up and say to the team - this is how it is, deal. But I'm a collegiate, work-with-not-against, bring everyone along, kind of person. Thankfully, it's really the PM's headache - I'm just there for support. An added complexity is that said PL's partner is due to have a baby any moment and they're taking a month off. Our general consensus is to wait until they're back because we do want them on board but there's stuff to get on with in the meantime.
There are pockets of use around the department and we have people who've used it in a past life and are real enthusiasts. I think it LOOKS great but big and complicated. In the interests of consistency, and as a way of getting people onboard, I think we should push for some proper training, with this particular project as the driver. So, I suppose we can begin making a business case for that whilst the PL is off, too? There is definitely a case for bringing the former, current and future users together to have a conversation - so far, I've sort of pin-balled around between individuals, which is one of the reasons I've felt I was getting nowhere. What I am keen on going forward is that I'm in a support/facilitation role and not driving the bloody thing!
The other main project I'm working on is moving out of workshopping and into development. And I'm taking over the RAPID log review process (that's a RAID + Principles - we're rather proud of it :D ) as part of my evidence gathering. The expectation is that I'll do the same for the new project. Anyway, it's going to result in the usual fun and games of finding a suitable hour in some very busy diaries *facepalm*
Oh, and I spent some time wresting with the Roadmap. There is stuff in the 'start in the next 6 months' box that has been there for at least a year because it's taken that long to get it into a format we're all happy with - ROFL. But it feels like we're shuffling to that point - and one of those projects is the new one mentioned above, so it might actually be the first thing to come OFF the Roadmap *feels giddy at the thought* And then we can move something in the '12 - 36 month' box up!
One move that seems very positive is we're trying to bundle some of the smaller things that come in via the project request form either into something that's already happening or with some of the other small things, to give us a critical mass of stuff. Again, the first project is an example - 3 pieces of work with a significant overlap of requirements has led to a single project, with the caveat that there's likely to be a pull in at least 2 different directions >D
But it's all good. I'm busy, and busy means employable. And it does feel like we're making the CIO happy - or at least happier!
In non-work, I'm up-to-date with 'Around the World' and 'The Tourist', and the new series of 'The Rookie' started this week. The opening episode was... I dunno - they had to wrap up the cliffhanger they left at the end of the last series, I suppose, but it felt like a LOT of compromises were made. Anyway, that's done, now, so I'll see how the rest goes. Still don't know how they've got 4 series out of a year-long process :D :D
I made some progress with my 70x700 novel, thinking about the central character's potential loss of humanity as a reaction to how everyone else treats them, and what jolts them out of it. Could be interesting - also could disrupt everything I've done so far, but it's all in plan form, which is easier to redo!
And I'm planning to run 8am online Sunday services during Lent with the Rector. I actually miss the online services, so I'm looking forward to it.
And that's all for now - bye for now DW!