What you need is a hammock task. A Hammock task is a task that depends on other tasks for both the start and finish dates. Like a hammock, the length of the task depends on the space between the two other tasks.
Roughly speaking, create a task, then link the start of the hammock task to the first task, and the finish of the hammock task to the second task. ...
They will do other work that needs doing. Keep in mind that "being in the sprint" means that the story is important. Not being in the sprint means the story is not that important.
Looking for something that falls in line with a person's specialty is nice, and making sure that over the long term your team's capabilities align with the kind of work requires ...
Both projects should have business cases tied to them. It should be relatively straight-forward for an appropriate authority to use these together with knowledge of your organization's priorities and decide.
Example. Project A should deliver $100 benefit. Project B should deliver $50 benefit. Resource goes to Project A.
Example. Project A should deliver $...
You are solving wrong problem
Your PM is completely out of control and #1 task is to get Projects back to PMs hands. They're now run by the Client and Developers, which is not really their job. .
There are many dangerous signs in case description:
"senior developer promised would be delivered over a month ago". What does "developer promised" mean? Isn't ...
Managing your resources--making tough decisions on how to deploy your financial, tools, materials, and humans--to minimize the threat of failure and maximize the likelihood of success AND treating people kindly, humanly, and with respect are two different things.
It is YOUR definition that makes a resource a thing. Dictionary.com defines it as: a source of ...
In certain cases it is possible to get more work done if you introduce more people.
The most usual scenario is when teams take time to do detailed scoping and when the project itself allows low coupling among the components.
In my experience this has rarely happened. Communication grows a lot by adding a single member and administrative tasks requiere more ...
Getting started with a distributed software development team
Welcome to PMSE! You said your team will be doing web and mobile development. Even though your question is very broad, I am taking a shot at an answer. If you have follow-on questions, please feel free to post them here as new questions.
Pick a development process - here is the super-short ...
This is a common issue where the PM needs a scarce resource, and there is insufficient capacity to allow all demands on that resource to be met. Ultimately, someone in the organisation has to make a judgement call. There are several options including the following - and there may be others:
Allocate the resource to one or other project;
Split the resource's ...
You have a few options at your disposal.
Use the available time to work on technical debts or fix bugs.
Ask the team member to share load another team member to help her/him in completing the sprint backlog because its a cross-functional team and its their shared responsibility / commitment to deliver sprint items as a team.
Pick the next highest priority ...
Don't sign the contract. Say no.
Look around at other industries. No other industry, EXCEPT IT, will you see this phenomena to this degree. Try it. Hire a builder and tell them they need to complete the house in three months instead of the six they told you. They'll walk away laughing.
For some reason, in IT, we say yes... and then fail.
Good question. I'm unclear on some of the details that inspire your question, so I'm going to provide three different answers
Risk Matrices are dangerous to your health.
I fall back to very crude ways of communicating priorities, by for example saying that a task or a project has "medium" priority.
Tony Cox and others have done some ...
When this happens, this is either a non-issue or the tip of a broader issue.
If both projects want Bob, but they don't need Bob and could use Jason instead but he's not quite as good, it's a non-issue. Maybe Bob goes to the harder project and Jason reaches out to Bob if he has questions.
Now, this becomes much more complicated if there is no Jason. If you ...
As Vadim suggests, it is crystal clear your PM capabilities are immature and under performing. It could be the abilities of the PM himself or a combination of the PM and organization systems and capabilities.
To solve the short term problem, to begin work on the second project before the first is signed off seems to be like continuing ad hoc, out of ...
You need to enter planning values for work packages, no matter the type. Your goal is NOT to be variance free. You will always accrue variances so you should not feel compelled to be so accurate with support package planning.
Choose your duration and load your support resources accordingly, based on the level of risk you wish to assume. If you are ...
This video shows how to organize the problem with a table, and proposes a simple greedy slack based heuristic solution: https://www.youtube.com/watch?v=7AJ73qxZtsI
This page http://www.pmknowledgecenter.com/dynamic_scheduling/baseline/critical-path-or-critical-chain-difference-caused-resources contains an awesome visualization of the problem with a single ...
Generally speaking, there is always something for people to do. They can help a colleague with their tasks, learn a new trick, write some documentation, clean up some code, talk with some other team, prepare a presentation on some useful topic, get people coffee, talk to a product owner or stakeholder about goals, learn about some existing piece of product, ...
Different tasks have different degrees of resources elasticity. And a task in itself can have different degrees of elasticity depending on other present variables like the environment.
Imagine ten patients needing surgery with one surgeon. Then, add four more surgeons. Would anyone argue that the duration to complete those surgeries worsened? Hope not. ...
As with all marginally performing employees, you sit them down, you outline expectations and achievable objectives, you detail a timeline, and then you measure for improved performance. This is essentially a PIP, a performance improvement plan. If he fails to meet the objectives, you cut bait and replace. Since this is a "project," your runway is very ...
You could model this in the Resource Calendar by having the Resource "work" only between certain times of the day on certain days of the week. Henceforth that resource can be applied 100% to a task but will nonetheless only perform work on the days/times on which you have declared it is available.
A downside of this will be that you will need to set it up ...
When I encounter this type of resistance I first email them (cc their supervisor) and ask to set up a face to face meeting. If this is not feasible, I change the email to address both employee and supervisor and schedule a phone conversation so the three of us can work out the issue(s) preventing completion of the tasks. It goes without saying that in all ...
The project manager is responsible for delivering the project and therefore making sure that the necessary amount of man power (with proper knowledge) is working - will work - on the project. Ideally, the PM should not start the project until the previous statement is ready, but that is rarely true unless the project requires rare expertise.
Usually, PMs ...
Since the PM knows what it takes to deliver the project, they have the best sense of what resources they need. So, in a typical scenario, the project managers ask for resourcing based on their own project needs, insulated from the organizations resources and other needs. This is typically referred to as the resourcing plan, and is aspirational. Then, ...
I am unsure why the official scrum guide has not been listed. The last time it was updated is Oct 11 but it is due to be updated this year.
Scrum Crazy links
The Scrum Kickoff Planner - Adam Weisbart
Essential Scrum Glossary - Innolution
Glossary of Scrum Terms - Scrum Alliance (Archived)
New Glossary of Scrum Terms - Victor Szalvay
It sounds as though the project is quite small, so I would personally not be assigning resources to tasks - it's not mandatory and, as you say, you are looking to schedule tasks.
Also, to say "what are the semantics of a resource in GANTT" isn't quite hitting the nail on the head...a GANTT chart is a project planning tool, and MS project is one software ...
Wikipedia defines a resource as follows:
A resource is a source or supply from which benefit is produced. Typically resources are materials, money, services, staff, or other assets that are transformed to produce benefit and in the process may be consumed or made unavailable.
Why People are "Resources"
People are the source of ...
Based on the information you provided:
How does one actually accomplish this?
In context of projects I suggest to start with optimizing the schedule for lead time (as opposed to minimum cost). Minimizing the lead time is a "regular scheduling objective" and as such can be scheduled using rule-based approach (simply put - easier).
Based on simple ...
I think I figured it out.
In the respective resource calendar -> work weeks -> details
the time for the allocated resource was set to:
08:00 AM - 10:00 AM
11:AM - 1:00 PM
I changed that to:
08:00 AM - 10:00 AM
1:00 PM - 3:PM
And project recalculated the duration correctly.
I have no idea what was wrong with the time which was set initially.
The screen shot does not show the field names, but it appears that you have a task Duration of 1 day (e.g. 8 hours), but Work set to 4 hrs (e.g. half a day). In order for resources to only work 4 hours on an 8 hour task, they must be set at 50%.
Looks like a growth opportunity to me!
The customer cannot know how much effort each piece of work takes.
The customer cannot know how much work you have already committed and how much bandwidth is left.
So, stop looking at it as someone is trying to slam you.
Make an estimate of each work item.
Is there any low priority work that you ...