I have been using JIRA for scrum for many years and its hard to imagine I would want to use any other tool. MPP is a great tool but in my humble opinion not for Agile.
Tom - it looks like Microsoft listened to your wish the current Manage Sprints dialog now includes option to add new sprints and to specify their durations to be other and 2 weeks duration.
Great Video. I have a question, if I have to follow up on many projects, that I delegate to my leaders to do the management. How do I continue projects with MS PJ Server? Can I use Sharepoint as a repository of my projects?
Hi, great video and very useful to a PM starting to use POL for managing projects and resources using the agile functionality. One question I have is if you manage your tasks in an agile way on the sprint or Kanban view does moving a task from one sprint to a later one update the delivery dates within the gantt chart view? I am finding if I move tasks around on the Kanban it doesn't change the deliver date for the task on the gantt chart view. This in turn doesn't show the enterprise resource in POL as being utilised in the right sprint/ date. What I can't see clearly is X task that takes X hours/ days that will happen between the start and end date of a sprint without a specific date and the resource utilisation in my reports. Hope this very long winded question makes sense!
I’m confused. Isn’t planning sprint 2 to the end against what SCRUM actually is? You’re missing values, user stories and you’ve actually planned all the tasks up front. Doesn’t SCRUM tell us to have stories in the product back log and plan the upcoming sprint in the last responsible moment (which is just the beginning of the new sprint) according to the values of the stories. Shouldn’t the tasks themselves be created during the sprint planning? What you’ve done seems like making a waterfall project seem like agile while it is definitely not agile at all.
Scrum requires that there is a goal for major time periods, but Sprints are just the updates on progress and communication between the moving parts to force modular teams to present needed pieces between the modules more efficiently. That doesn't mean you don't need to have some idea of what's needed in the project, about how long each piece can take, and some idea of the major goal. A waterfall framework gives you the ability to lay out the major portions of the project and where each would or should be available to start, where each should come to its basic end (even though it may take on adjustments down the line, some basic functional end is a good idea to mark), and where the project is viable for more public presentation (ideally a functional product that can be handed off). Smaller pieces of the project--especially with respect to different modular teams, groups or departments--or the piecemeal processes handled by multiple small groups or contractors can be followed and included in sprints, and can follow the principles of SCRUM, sitting as the underlying tasks of the larger pieces of the project. By finishing those smaller tasks and using sprints to facilitate the communication necessary to move forward, using scrum as your working model among the modules, you can then keep track of a larger project and all the resources, their effectiveness, and any extensions in the timeframe that may become necessary to the endpoints within the project. When your boss or the client calls, they don't give a damn about your sprints or the stories. They want a timeframe overall, which is where the waterfall is a better serving view. Kanban is a great view working within a single small group of similar skillset employees, since they can grab a task and get to work, then note it finished or note difficulties. It still may require the sprint every day or every other day for the team leader to keep the team mobile, and be capable of carrying those stories to the weekly sprint if necessary, but the end result is the same; the information still needs to be available in some overall listing. This shows how well that can work in MSProject.
I started my project from scratch and when I converted to Agile methodology, only see 3 default sprints, I have 24 sprints in my project, how can I add those sprints. Thanks!
While MPP has started on this, I think it is far away from really making it useful for practical purposes. Where is burn down? Do you still need a PM to manage this? MPP is outdated like Nokia phones in android world.
I have been using JIRA for scrum for many years and its hard to imagine I would want to use any other tool. MPP is a great tool but in my humble opinion not for Agile.
This was an excellent overview! Thank you so much, Tom! :-)
Great video. I was trying to figure out a few things. Your video has covered most of them. Thanks Tom!
PLEASE, emphasize what type of MS-Project Scrum option is included so that we can be on the same page - ONLY Project online has this option.
Tom - it looks like Microsoft listened to your wish the current Manage Sprints dialog now includes option to add new sprints and to specify their durations to be other and 2 weeks duration.
Great Video. I have a question, if I have to follow up on many projects, that I delegate to my leaders to do the management. How do I continue projects with MS PJ Server? Can I use Sharepoint as a repository of my projects?
Hi, great video and very useful to a PM starting to use POL for managing projects and resources using the agile functionality. One question I have is if you manage your tasks in an agile way on the sprint or Kanban view does moving a task from one sprint to a later one update the delivery dates within the gantt chart view? I am finding if I move tasks around on the Kanban it doesn't change the deliver date for the task on the gantt chart view. This in turn doesn't show the enterprise resource in POL as being utilised in the right sprint/ date. What I can't see clearly is X task that takes X hours/ days that will happen between the start and end date of a sprint without a specific date and the resource utilisation in my reports. Hope this very long winded question makes sense!
Outstanding Video! Thank you so much!
well put together.. thank you
I'm using MS Project Pro 2019, and no Agile button. :/
I’m confused. Isn’t planning sprint 2 to the end against what SCRUM actually is? You’re missing values, user stories and you’ve actually planned all the tasks up front. Doesn’t SCRUM tell us to have stories in the product back log and plan the upcoming sprint in the last responsible moment (which is just the beginning of the new sprint) according to the values of the stories. Shouldn’t the tasks themselves be created during the sprint planning?
What you’ve done seems like making a waterfall project seem like agile while it is definitely not agile at all.
Scrum requires that there is a goal for major time periods, but Sprints are just the updates on progress and communication between the moving parts to force modular teams to present needed pieces between the modules more efficiently. That doesn't mean you don't need to have some idea of what's needed in the project, about how long each piece can take, and some idea of the major goal. A waterfall framework gives you the ability to lay out the major portions of the project and where each would or should be available to start, where each should come to its basic end (even though it may take on adjustments down the line, some basic functional end is a good idea to mark), and where the project is viable for more public presentation (ideally a functional product that can be handed off). Smaller pieces of the project--especially with respect to different modular teams, groups or departments--or the piecemeal processes handled by multiple small groups or contractors can be followed and included in sprints, and can follow the principles of SCRUM, sitting as the underlying tasks of the larger pieces of the project. By finishing those smaller tasks and using sprints to facilitate the communication necessary to move forward, using scrum as your working model among the modules, you can then keep track of a larger project and all the resources, their effectiveness, and any extensions in the timeframe that may become necessary to the endpoints within the project. When your boss or the client calls, they don't give a damn about your sprints or the stories. They want a timeframe overall, which is where the waterfall is a better serving view.
Kanban is a great view working within a single small group of similar skillset employees, since they can grab a task and get to work, then note it finished or note difficulties. It still may require the sprint every day or every other day for the team leader to keep the team mobile, and be capable of carrying those stories to the weekly sprint if necessary, but the end result is the same; the information still needs to be available in some overall listing. This shows how well that can work in MSProject.
You also did not cover the "Agil" feature that was on the same ribbon... Why?
Please, I Have microsoft project 2016 plus, but I can't see the option "Agile" that shown in the video. what should I do?
Good question. Same here. I have done the updates
I started my project from scratch and when I converted to Agile methodology, only see 3 default sprints, I have 24 sprints in my project, how can I add those sprints. Thanks!
Mariela Williams Sprints are based on the duration of your project. Adjust the duration of your project and they will be created automatically.
my project 2016 is 1711 build but does not have that agile option :/
Hi Fabricio,I just looked and I have build 1712! you will need to update your software using click to run.Hope this helps
But this functionality appeared in the 1710 right?
Fabrício Araújo I’m not sure. If you don’t have it I would assume not! Do you have a subscription?
Yep
Fabrício Araújo update your software then mate!
link of the file?
While MPP has started on this, I think it is far away from really making it useful for practical purposes.
Where is burn down? Do you still need a PM to manage this?
MPP is outdated like Nokia phones in android world.