canonical-ci-engineering team mailing list archive

[Ursula Junque <ursula.junque@xxxxxxxxxxxxx>]

On Wed, Apr 1, 2015 at 11:59 PM, Thomi Richards <
thomi.richards@xxxxxxxxxxxxx> wrote:

> Hey,
>
>
>
> On Thu, Apr 2, 2015 at 3:13 PM, Celso Providelo <
> celso.providelo@xxxxxxxxxxxxx> wrote:
>
> <massive snip>
>
>>
>> Yes, it is a cheat. Stakeholders do not care about *the code*, it's just
>> our 'instrument' to provide them value. Strictly speaking we should only
>> care about *the code* when it is affecting the how we deliver value, either
>> reducing our velocity (which is your _valid_ point) or prevent us to solve
>> problems.
>>
>> <massive snip>
>
>
>> CI-CD (highly automated, instrumented and monitored production
>> environment) is a very important aspect of the way we intend to deliver and
>> maintain solutions and was entirely overlooked for one and half sprint.
>>
>>
> It seems to me that our stakeholders really don't care about CI/CD either,
> right? Surely they'd be perfectly happy if we  had to manually deploy
> services using nothing but a magnet and a rusty nail, as long as they got
> deployed?
>

Not really, if that slows us down and our solution carries a huge
operational burden, they will be impacted by our inability to work on new
features because we're busy cleaning things up. They already know that. :)
I think we need to find balance between delivering useful stories and
taking care of not creating more technical debt, by incrementally
introducing more maintainable services. This doesn't mean we'll necessarily
deliver perfect solutions, but we'll consider these when planning and act
accordingly, like we're starting to do.


> *We* would care, because it'd slow us down.
>
> Of course I think we need proper CI/CD, just as I think we need to write
> good code. It just seems that scrum (or at least the way we're doing scrum)
> doesn't help us do these things.
>

We are realizing these things are missing before they become legacy and
having the chance to do something about it. That's because of scrum. :) The
challenge with scrum is to be able to convince stakeholders when it's
absolutely necessary that we work on solely infrastructure/background
things. We were able to work on the proposed-migration scalability problem,
we can do that again if we have an equally compelling argument. :)


>
> Cheers,
> --
> Thomi Richards
> thomi.richards@xxxxxxxxxxxxx
>



-- 
Úrsula Junque
Ubuntu CI Engineer

ursula.junque@xxxxxxxxxxxxx
ursinha@xxxxxxxxxxx
ursinha@xxxxxxxxxx

Ubuntu - "I am what I am because of who we all are."
Linux user #289453 - Ubuntu user #31144