Public:Resource Allocation - Revision history

Tushar Goswami: Tushar Goswami moved page Resource Allocation to Public:Resource Allocation

2024-07-13T08:33:35Z

Tushar Goswami moved page Resource Allocation to Public:Resource Allocation

← Older revision	Revision as of 14:03, 13 July 2024
(No difference)

Mayank Gupta at 06:53, 2 July 2024

2024-07-02T06:53:31Z

← Older revision		Revision as of 12:23, 2 July 2024
Line 17:		Line 17:
	== What's the schedule of the colleague ==		== What's the schedule of the colleague ==
	Your selected colleague might already be occupied in some other work. Check with Project Manager, CXO, as well Finance team on the priority of the work the colleague is working on. If its OK then you can ask their Project Manager to communicate the new priority to them		Your selected colleague might already be occupied in some other work. Check with Project Manager, CXO, as well Finance team on the priority of the work the colleague is working on. If its OK then you can ask their Project Manager to communicate the new priority to them

			== Examples ==

			# [https://docs.google.com/document/d/1Bj4IUSiEsITiEIeqTbreA03TdpNteX5EHwS0EEOzc7U/edit?usp=sharing Internal: Synterex - Resource Allocation"]
			# [https://docs.google.com/document/d/1xF8wIN0zPjkHaDzgBBV-lIZwNYO-snqZLROy8ISIQw0/edit?usp=sharing Internal: Numerik - Resource Allocation]

	[[Category:SOP in Project Management]]		[[Category:SOP in Project Management]]

Tushar Goswami: /* What skills are needed to do the task */

2024-06-25T14:28:39Z

What skills are needed to do the task

← Older revision		Revision as of 19:58, 25 June 2024
Line 11:		Line 11:
	== Which colleague has those skills ==		== Which colleague has those skills ==
	Use [[Grading as well as feedback\|Grading sheets]] to find out which colleague has those skills. Often very high level artifacts are graded there, but low level skill aren't graded there. Take guidance from [[CXO]] of the department to verify that your selection of colleague is right		Use [[Grading as well as feedback\|Grading sheets]] to find out which colleague has those skills. Often very high level artifacts are graded there, but low level skill aren't graded there. Take guidance from [[CXO]] of the department to verify that your selection of colleague is right

			== Ideally how fast you want it finished ==
			market forces or clients would require to finish the work by a certain time

	== What's the schedule of the colleague ==		== What's the schedule of the colleague ==
	Your selected colleague might already be occupied in some other work. Check with Project Manager, CXO, as well Finance team on the priority of the work the colleague is working on. If its OK then you can ask their Project Manager to communicate the new priority to them		Your selected colleague might already be occupied in some other work. Check with Project Manager, CXO, as well Finance team on the priority of the work the colleague is working on. If its OK then you can ask their Project Manager to communicate the new priority to them
	[[Category:SOP in Project Management]]		[[Category:SOP in Project Management]]

Tushar Goswami: Created page with "Resource Allocation is done when you've tasks figured out and you want to assign the right people to the right task. But often we wrongly assume that we've the task figured out, and we make the mistake of assigning people to the task even when the task is not mature enough. Go back to Strategy Room to ensure that your tasks are mature enough before assigning the people to it = Steps = == What skills are needed to do the task == Its common to assume high level skil..."

2024-06-04T01:47:40Z

Created page with "Resource Allocation is done when you've tasks figured out and you want to assign the right people to the right task. But often we wrongly assume that we've the task figured out, and we make the mistake of assigning people to the task even when the task is not mature enough. Go back to Strategy Room to ensure that your tasks are mature enough before assigning the people to it = Steps = == What skills are needed to do the task == Its common to assume high level skil..."

New page

Resource Allocation is done when you've tasks figured out and you want to assign the right people to the right task. But often we wrongly assume that we've the task figured out, and we make the mistake of assigning people to the task even when the task is not mature enough. Go back to [[Strategy Room]] to ensure that your tasks are mature enough before assigning the people to it

= Steps =

== What skills are needed to do the task ==
Its common to assume high level skills like "Python". At Smarter.Codes we go as low level as possible to define the skill. Ideas for skills

* Pick an [[Artifact]]
* Define your skill as low-level as possible. Example : Python > [[pythoninfo:PythonSpeed/PerformanceTips|Performance Optimization]] > [https://stackoverflow.com/questions/3927628/how-can-i-profile-python-code-line-by-line Line Profiler]

== Which colleague has those skills ==
Use [[Grading as well as feedback|Grading sheets]] to find out which colleague has those skills. Often very high level artifacts are graded there, but low level skill aren't graded there. Take guidance from [[CXO]] of the department to verify that your selection of colleague is right

== What's the schedule of the colleague ==
Your selected colleague might already be occupied in some other work. Check with Project Manager, CXO, as well Finance team on the priority of the work the colleague is working on. If its OK then you can ask their Project Manager to communicate the new priority to them
[[Category:SOP in Project Management]]