Introducing The Ultimate Agile Project Management Software

Introducing The Ultimate Agile Project Management Software

[Music Intro]>>Hi. I’m Devin Deen, Content Director here
at Hi, welcome to today’s whiteboard session. Over the last few weeks,
we’ve had a lot of requests from you users out there, about how to use this Agile project
management software on an Agile project. So I’d thought what I’d do today is take the
opportunity to show you how I would use it and how I use when I’m
doing Agile projects. I’d be certainly interested to hear your feedback
on my approach and certainly, give us some feedback on how you’re using it on an Agile
project. Remember once again, if there are any features that you’d like to see on the
project stack, make sure you click on the “request a feature” button which we’ve just
enabled, and that request will get into our development team. So, first off, the most important thing is
that Agile project communication and collaboration are key. All those sorts of philosophy and
that concept is built into the service, so use all the features per normal.
I would not use all the features, certainly use the issues, use the scheduling, use the
document repository, messaging; all that is very important in terms of communication and
collaboration and none of that goes out the window just because you’re doing an Agile
project. Use all the features as per normal. What the difference is how you actually organize
your tasks, how you manage your changes, and then how you track it. I’m just going to focus
in on those three items for the moment. As you know, in an Agile project, you’ve got
your story, you’ve got your backlog of requirements and then you’ve got the tasks that go into
making the backlog possible, delivering on that set of prioritized requirements. The
chart within is there for you to use. Most people use it in the traditional
waterfall manner, but if you’re doing an Agile project, use a Gantt chart, but don’t put
your task in there like a normal traditional waterfall project. Put your start and end date for the task to
be the same for all the tasks. Take the particular tasks that you’re going to do in that particular
sprint, list them in the columns on the left tasks to do; definitely put your resources
on them, put your effort estimate, but on the start and end dates, put the start date
as the start of your sprint, and the end as the end date of the sprint. You’ll basically
have a column of tasks with start and end date for that particular sprint. The next thing you do is your changes. In
the change module, that’s where you would traditionally put any of the change requests
that come through from your project stakeholder and your user group. I would use the changes
module to track your backlog. Put your list of requirements in there. Every item on the
backlog goes into the change repository and you can identify which of those that you’re
doing for each sprint. The reason why I do this is because in Agile project management,
items in the backlog drop in and drop out as the team progresses through the sprint.
So the best place to keep the list of backlog requirements is in the change module. That’s
where I would put all the backlog, put it in your changes and track which ones are being
done in each of the sprints that you’re doing to achieve your end result. Lastly, how do you actually track that Agile
project manager using project web service? Well, in an Agile project, the
things you’re going to focus on and the number of task you’re completed in a given day in
that sprint and how many hours have been expended on every day of the sprint. Same principles
apply here using the service, you’ll be able to get a report if your team
members are using the timesheet module. They’ll be able to put in the amount of time they’re
doing against each of the tasks. You can run a report at the end of the day to figure out
which if the team members are completing their task, which tasks have been completed and
how many hours have been expended up to date. By getting that information you can pull that
together in a spreadsheet and put it in your status report for your burn chart. There’s some really simple ways to use the
service in an Agile project. I’ll be very keen to hear your feedback, and if you’re
doing Agile projects using, and certainly, once again, if there’s any
features that you’re not seeing in there that you want to see, in particular doing Agile
projects, certainly request that on the request feature. Thank you very much, have a great day. For
more project manager whiteboard sessions and all your project manager needs, come see us

3 thoughts to “Introducing The Ultimate Agile Project Management Software”

  1. Hi Devin, love the vids and I'm taking a management class now.
    I also have a birthday coming in 2 weeks, have you ever sneezed in a vid?

Leave a Reply

Your email address will not be published. Required fields are marked *