Not sure if you ask about project plan or something else. Here’s an article I have: pmbasics101.com/project-planning-beginners-27-simple-steps/ Let me know if you asked something different.
Yes, we do. But keep in mind that we should go one or two levels up from User Stories. In RTM in agile environment, you should opperate with Epics or Epic Themes.
Dear Dmitriy, As a part of scope management ->, collect requirement -> then make the RTM -> then define the scope statement document, but I don't where does the SRS fit in, is the SRS and RTM same, my project is an online delivery app in python, do I only have RTM or SRS? please guide me with your expertise Dmitriy..thank you
SRS stands for Software Requirements Specification. In classic meaning it’s a long document that describes functionality and capabilities of an application. But it’s only one form. You can get specification as a series of documents that describe different parts of the application. Or you can go agile and create User Stories. So, there are different types of requirements specification. If you have one big specification, in RTM you most probably will point to specific parts of the document. RTM will help you break down a big list of requirements into smaller pieces. But I rarely see this nowadays. More often, you get specification in small pieces and in different forms (verbal, slide decks, emails, etc). You put it all into different small specification (read doc files, wiki pages, User Stories). RTM helps you to organize and track progress on all these different pieces. In software development, I recommend avoiding long specifications and use agile approaches. In this case, you need RTM only if the product you develop is complex. Instead use Features and User Stories to organize your requirements.
Good question, Letsema. Yes, it can be used for non-IT projects. You can use it the same way in construction. The only different is the form of specification that you use. But you should simply link to the corresponding documents.
It depends on how you spent those 6 years. If you just followed the orders and did what you are told - it will be hard. Project Manager’s role is all about responsibility, initiative, and leadership. So, if you can find examples where you did something beyond the call of duty for a QA engineer you can easily become a PM. Think about micro projects where you lead a group of people to improve something. For example, processes, tools, or techniques. Or examples, where you communicated with stakeholders to drive them in the right direction as an experts. Mentorship is also a relevant experience. And so on. When you are in the IT industry your leadership skills are more important than anything else. And it’s much easier to get a promotion to a PM then in other industries because there are always smaller projects that you can start with. Check out this guide as well. It answers lots of questions: pmbasics101.com/it-project-manager/
![Scope Management: Everything You Need to Know? [Comprehensive Guide]](http://i.ytimg.com/vi/jw58KqqCb58/mqdefault.jpg)
👉Discover How to Land a Senior IT Project Manager Job…
…so You Can Finally Get the Fulfillment and Recognition You Deserve
itpmschool.com/workshop/
The Matrix is everywhere. It is all around us.
MORPHEUS ))
LOL
Thank you so much for the explanation.
You are welcome, Bothka!
Great Tutorial, thank you
You’re welcome, Paul. Glad it’s helped.
Really awesome video, much appreciated! Is there a video for implementation plan/ action plan? Thanks
Not sure if you ask about project plan or something else. Here’s an article I have: pmbasics101.com/project-planning-beginners-27-simple-steps/
Let me know if you asked something different.
Thank you for this!
You are welcome, Paula!
I love your videos❤
Thank you!
"I'll wait so you can do it right now" + pregnant pause. You're funny. Good on you.
Thanks for the good helpful content. Much appreciated.
Glad it was helpful!
Thank u for this
Sorry, I missed your comment. If it's still actual, please write a new one.
Note: leaving this comment to keep track of open questions.
Really awesome video! Thank you!
Glad you liked it!
Do we use RTM in an agile process?
Yes, we do. But keep in mind that we should go one or two levels up from User Stories. In RTM in agile environment, you should opperate with Epics or Epic Themes.
Dear Dmitriy, As a part of scope management ->, collect requirement -> then make the RTM -> then define the scope statement document, but I don't where does the SRS fit in, is the SRS and RTM same, my project is an online delivery app in python, do I only have RTM or SRS? please guide me with your expertise Dmitriy..thank you
SRS stands for Software Requirements Specification. In classic meaning it’s a long document that describes functionality and capabilities of an application. But it’s only one form. You can get specification as a series of documents that describe different parts of the application. Or you can go agile and create User Stories. So, there are different types of requirements specification.
If you have one big specification, in RTM you most probably will point to specific parts of the document. RTM will help you break down a big list of requirements into smaller pieces. But I rarely see this nowadays.
More often, you get specification in small pieces and in different forms (verbal, slide decks, emails, etc). You put it all into different small specification (read doc files, wiki pages, User Stories). RTM helps you to organize and track progress on all these different pieces.
In software development, I recommend avoiding long specifications and use agile approaches. In this case, you need RTM only if the product you develop is complex. Instead use Features and User Stories to organize your requirements.
Can this be used on non IT projects, like in construction etc
Good question, Letsema. Yes, it can be used for non-IT projects. You can use it the same way in construction. The only different is the form of specification that you use. But you should simply link to the corresponding documents.
Also, is there a video you’ve made specifically for creating WBS?
I don’t have a video on WBS but I have a great in-depth article. Check it out here: pmbasics101.com/work-breakdown-structure-guide/
Can a QA with 6+ yrs exp become project manager?
It depends on how you spent those 6 years. If you just followed the orders and did what you are told - it will be hard. Project Manager’s role is all about responsibility, initiative, and leadership. So, if you can find examples where you did something beyond the call of duty for a QA engineer you can easily become a PM. Think about micro projects where you lead a group of people to improve something. For example, processes, tools, or techniques. Or examples, where you communicated with stakeholders to drive them in the right direction as an experts. Mentorship is also a relevant experience. And so on.
When you are in the IT industry your leadership skills are more important than anything else. And it’s much easier to get a promotion to a PM then in other industries because there are always smaller projects that you can start with.
Check out this guide as well. It answers lots of questions: pmbasics101.com/it-project-manager/
Ahahaha haha
Ho-ho-ho