2 ms·
for projects as service ( like consulting ) use kanban but incorporate epics and sprints where epics are communicated to the client as just "phases" and sprints
by chasd00 9y ago
for projects as service ( like consulting ) use kanban but incorporate epics and sprints where epics are communicated to the client as just "phases" and sprints are internal to the developer team.
your PM should also be able to do at least some solutioning. The best projects i've worked on where ones where the PM was also the Solution Architect.
Every projects gets a TL ( tech lead ). This is the PM/SAs right hand goto person. The TL handles the design and implementation of the SAs vision. They also manage task delegation to the dev team, and acts as their escalation point. The TL must be able to get up in front of the client and explain technical jargon in a way the client understands it.
process = Kanban + epics/sprints
Staff = 1 PM/SA, 1 TL, Dev Team
I've seen the above work very well in consulting for projects in the $2-3M budget range.