This document is intended to be a superset of all the things that might be
required of a transformation partner. Some will take delivery
responsibility, so not. Some will need to look at legacy
system integration and/or migration, some not. It depends on the department
and the project. I need to make this clear - I'll add a note. Thanks.


On 26 March 2013 14:01, Kushal Pisavadia <notifications@github.com> wrote:

> In service-manual/service-managers/transformation-partner.md:
>
> > +  - alpha
> > +  - beta
> > +breadcrumbs:
> > +  -
> > +    title: Home
> > +    url: /service-manual
> > +  -
> > +    title: Service Managers
> > +    url: /service-manual/service-managers
> > +---
> > +
> > +Many departments will find it useful to engage with a partner who can help build digital capability within the department at the same time as working with them to deliver working digital service. In selecting a supplier as a digital transformation partner for the department, these are some of the things that we'd like to see.
> > +
> > +## Track Record of Delivery
> > +
> > +The partner needs a proven track record of successful delivery, and will take responsibility for the delivery of the digital service.
>
>  and will take responsibility for the delivery of the digital service
>
> I'm not sure I agree with this line. At Sprint 13 this was a major
> discussion point amongst department members I spoke to. They
> procured/contracted a supplier who would take on responsibility but in the
> end it was the departments whose reputation was on the line.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/alphagov/government-service-design-manual/pull/58/files#r3531223>
> .
>



-- 
Cheers,
Simon B.