Noob PM here - I have a project with 3 developers (one of whom is tech lead), a BA, and a tester. The tech lead (hereafter referred to as TL) is responsible (on the RACI) for the technical output of the team, i.e actually delivering the software.
TL would like to deliver the project using a kanban-like methodology, and has asked the BA to deliver high level epics which they have then together broken into stories. This was all pre-project. Now the project has kicked off, TL has organised planning meetings which everyone is attending, with the view of breaking down the stories into tasks and estimating.
However, at first planning meeting another of the developers who had worked closely with the business area in question to produce a very basic proof of concept as part of our requirements gathering, rejected the approach out of hand, saying that there was no point in going back to basic user stories when we already understood most of the process and what needed to be delivered, and refused to take part in the task break-down and estimation activities.
TL has recently come to me and stated that they can no longer be responsible for the output of said team member. I'm at the point where I don't care what methodology they use but we need to get started and I am unsure how to intervene (or if I even should) to best continue.
- Is there another methodology I can suggest which will mollify the team member who doesn't want to estimate tasks, and also give us the ability to be agile and transparent in our delivery?
- Would it be feasible to allow said developer to continue along their line of development in parallel to the rest of the team and somehow allow the two resulting solution-strands to merge at some point?
- What would any of you do in my place?
Thanks for your advice.