Corporate plans: what is wrong?
Norway Gun joined a new startup in Silicon Valley.
He was appointed as Lead hence he is in JavaScript technologies. Company HR asked to Norway before joining about the lead experience. Norway told her “Yes he has 3 years’ of experience as a lead”
After joining 15 days passed for access and installations. Another 15 days passed for roles and access request to client and received.
During that time he gets to know that application is using some different technology which Norway not aware of. He asked to his manager about that, but his manager told – “no need to worry about. He has to run only scrum as what the entire user story picked up and when to be completed”
Norway appointed as Technical lead and his project is using .Net & C# in backend. It’s anyway not too possible for him to update and run with the new technology in few months. But if he agreed with his manager`s point that to run as scrum master he quite okay with that. Norway does not able to take decision now. He wants to see the challenges and thought, he will decide it later.
Now after completing some more months it became challenges to find out, how he manage his role into this project. He digs into that and find out the reason why and when it can be possible.
He found three challenges into this,
- Technologies: Find out the technologies what team using to create application. Try into learn on his pace as possible. Now most of the application is not based out of one technology, so other many added frameworks or tools added into it. So now if he plans to spend 2-4hours weekly to learn, then at least he will be required 48-50 hours for basic knowledge. Additional tools required additional hours like Web APIs. So in the bottom line If he will spend even 6 months, he will be aware of with basic understanding and more 6 months at least be required to be excellent. So Is this a good deal to do that or he should looking project in his own skills set, which he has knowledge with.
- Knowledge of Business: This point is another face point for new joiners into the project and every time one BAs` should be available for each of the story point. Normally when projects runs, BAs` have own work so mostly he will not be available. If any story point even shared the business knowledge, you have dependency for other story business knowledge too which may be part of the query and your story linked with. If BAs` also a new joiner, this is again an issue and you have to find out a person who are older than you in the project. One solution is fine here for one point of contact, but it depends. If this project is one man`s show, then difficult to get time and you never being progress with time.
- Support from Leads/Members: It is another important point for new joiners in lead roles, because in early days many team members take it differently. Like Jonathan has spent some hard hours into the same project, so as per Jonathan, he must be appropriate for this role. Why organization hired new resources? For this attitude Jonathan never support Norway. Jonathan may be not similar experience like Norway but he aware of those technology which new for Norway.
Project is like a team effort like cricket/football match and when all members in team put their efforts constantly, then it succeed. Else it’s really difficult. So the question is what we are planning for?
Everyday team schedules a meeting to discuss project plan, but no one why not looking into this. Is Norway`s manager knows about it? Who should be looking spill over things like what we are discussing?
A project work is bread and butter for all members who are working but some urgent issues need to plan and fix by authority. Else Norway may leave the organization or try for next option. But who is benefitted in this case.
Company, who already paid for Norway?
Manager who belief Norway will be suitable and again he will appoint another Norway to make light budget?
Or finally Norway, who already spoil his few months into this project?
Still we need to think this corporate plan.
Comments