12
votes
What to do with work not on the board?
TL;DR
If the work matters, make it visible. If it doesn't, then treat it as muda and trim it as non-essential waste. You truly cannot have it both ways.
"No Invisible Work, Ever!"
CodeGnome'...
12
votes
Accepted
What to do with work not on the board?
You can have a technical leader. You can have him do work off the charts. You can hide this work from others that don't "need to know". You can reduce that person's capacity to make planning more ...
5
votes
Accepted
WBS and agile approach
No, the WBS is not outdated, obsolete, deprecated, nor useless.
The WBS is just a decomposition of WHAT you want to deliver.
Building a WBS is not a one-shot task, but it is an interactive and ...
4
votes
Work Breakdown Structure - Help on identifiying deliverables, workpackages, etc.,
The first thing you need to do is remove those phases. They are straight from the PMBoK and are process groups, not phases. Trying to organize your work around that will yield nothing useful. In ...
3
votes
How do I make a Gantt Chart where the project execution phase in the WBS is modified to implement Scrum?
Why are you attempting to produce a Gantt chart?
I suggest that you read the Scrum Guide as this will provide a background into relevant Scrum artifacts.
I expect the real reason is that the ...
3
votes
Work Breakdown Structure - Help on identifiying deliverables, workpackages, etc.,
Deliverables depend entirely on what you are building. You may find it best to start by stating the end result of the project then work backwards to find the interim deliverables. In the case of a ...
3
votes
How can a project manager create a plan without having specifications for the product defined at the beginning of the project?
How does a project manager manage planning without the specifications of the product at the beginning of the project
With difficulties.
Without knowing the specifications, you need to make ...
2
votes
How long should a work breakdown structure take to create?
The complexity of your product the project is creating dictates how the complexity of your WBS. Can you imagine what the WBS of a fighter aircraft looks like? However, one person would not be ...
2
votes
WBS and agile approach
I agree that the by strict definition of a WBS and its use lends itself to best be used in the waterfall methodologies...however like mentioned above some of its principles can be applied to managing ...
2
votes
Should we break each smallest possible thing as a separate story?
I've some considerations about this question.
I would try not to explicitly define in the Story the complete list of pages, one by one. Guess the pages are forty, instead of four.
So my approach would ...
2
votes
Accepted
What is ""action-oriented" WBS Item?
In the context of the rest of the section, it is saying that you should focus on the outcome desired, not the action needed to get there. For example, I might say that I should have infrastructure ...
2
votes
What to do with work not on the board?
From the Scrum Guide:
Scrum is a framework for developing, delivering, and sustaining
complex products.
Everything in Scrum is centered around the development, delivery, and maintenance of ...
2
votes
Backlog - Is this to (i) List outstanding 'user stories' or (ii) List outstanding 'tasks' or (iii) Can one be used for both purposes?
The Scrum Guide does not say that a backlog item has to be in the form of a user story. You may write the backlog item the way you like, or more precisely the way the team prefers it to be.
2
votes
Backlog - Is this to (i) List outstanding 'user stories' or (ii) List outstanding 'tasks' or (iii) Can one be used for both purposes?
Backlog should contain all workable items
According to Scrum Guide:
Product Backlog is the single source of work undertaken by the Scrum Team.
So in my opinion the Backlog should contain all ...
2
votes
Do you update your Work Breakdown Structure document once requirements have been defined?
I think there is a frame mismatch here, and I don't think the question can be authoritatively answered unless the frames are clarified. My discussion below is very explicitly not to challenge or ...
2
votes
How can a project manager create a plan without having specifications for the product defined at the beginning of the project?
There are a few options.
One option would be rolling-wave planning. Perhaps some aspects of the project, such as the end date, are known and can be laid out. You may be able to plan enough work to ...
1
vote
Project management: WBS dictionary
Who is evaluating your WBS Dictionary? If your WBS Dictionary is a deliverable that requires "acceptance" from the buyer, then you need to meet the requirements of that buyer. If you are only ...
1
vote
Accepted
Combining WBS structure types; deliverable oriented and task oriented
A product oriented WBS would have products on top, broken down to its manageable sized components, and then activities below it. I define the work package to be the lowest level of product; the ...
1
vote
What should I learn to become a software project manager?
I am a software project manager. When I started my journey in project management career, I took this course in course. It was really helpful to build the foundation for Sprints, dividing the work etc: ...
1
vote
WBS and PERT diagram
Your network diagram should show all leaf level WBS elements in the sequence as indicated in your work logic. So milestones would be included. You may not show the phase necessarily but if you ...
1
vote
Accepted
WBS and PERT diagram
Early versions of PERT diagrams had "PERT Events" that were all milestones or gates with task information embedded in the arrows. This has changed over the years but most PERT charts I have seen "in ...
1
vote
Accepted
Accurate estimation using work break down structure (WBS)
I would like to say that it is better to replace Work Breakdown Structure with a Requirements Breakdown Structure. So you can copy and past your Requirements Breakdown Structure from Requirements ...
1
vote
Project Gantt Chart tasks breakdown question
There is no single right answer to this question - it depends entirely on the level of control that you need or want, and the level of reporting and monitoring that is required.
As a rule of thumb, ...
1
vote
WBS and agile approach
You can split your customer business goals -> on Epics, Epics -> on User Stories or Features. And think about it as about WBS. But there are significantly important things to take into account:
You ...
1
vote
Accepted
WBS and Project Planning
Even Agile can have some initial planning and artifacts produced. I described it here. So, it's totally ok, if your roadmap starts with "Onboarding and initial backlog creation" phase/sprint/milestone....
1
vote
WBS Common Work/Deliverable
Either works. "A" looks more logical and would likely be easier for other stakeholders to consume but "B" is fine, too. In "B", your dev task is acting like a hammock activity.
What is most ...
1
vote
WBS Common Work/Deliverable
There isn't a lot of information in your question, so I'm having to make some assumptions, but I think your second diagram is correct.
If the
Deliver Customer processing module depends on "develop ...
1
vote
Accepted
How to model extended period of 'searching for product' tasks in MS-Project?
Have a single task "Acquire 200 items" with a 2-month duration
You can have a single task named "Acquire 200 items" with a 2-month duration. If, for example, at the end of one month you have acquired ...
1
vote
Should we break each smallest possible thing as a separate story?
Depends on the size of the story.
If it is < 2 h per page than you should be pragmatic and merge them based on different criteria.
If it is more than a day then separated stories makes sense.
1
vote
How do I make a Gantt Chart where the project execution phase in the WBS is modified to implement Scrum?
You are not going to like this; the answer is you cannot.
A Scrum project can ally to a release plan but a Gantt chart is the antithesis of Scrum.
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
work-breakdown-structure × 60planning × 10
ms-project × 6
agile × 5
estimation × 5
scrum × 4
gantt × 4
requirements × 3
tasks × 3
cost-management × 3
scope × 3
schedule × 3
deliverables × 3
software-development × 2
user-stories × 2
backlog × 2
task-management × 2
dependencies × 2
project-management-style × 1
scrum-master × 1
communication × 1
pm-software × 1
scheduling × 1
process × 1
methodology × 1