Related Posts
Hi guys
I am working in Tata Consultancy kolkata from past 3 years, planning to get transfer to TCS Bangalore(hometown). Will there be any issues if I provide fake medical certificate for my parents? Also now they are forcing me to come back to kolkata office, is there any possibly they may let me work from bangalore office even if my project ODC is not there in bangalore?
Tata Consultancy
More Posts
Hey,
SALESFORCE is looking for a full stack or UI developer 4+ years of experience.In case anyone is interested, I can refer you.
You can dm me or send me your resume and interested joblink or id at zeuskype@gmail.com
Full Name :
Phone number:
Country phone code:
Email id :
Linkedln link :
Any recruiters from Target on here?
Additional Posts in Product Management
How does a Microsoft PM differs with Google PM?
New to Fishbowl?
unlock all discussions on Fishbowl.
One project board per product. The board is broken down into swim lanes so different areas of focus can view their sub tasks. And as a PM I can have a high level view of whats in motion or completed. Different views can also be created within the project if needed - so if for any reason the engineering team thinks the swim lanes are difficult, they could have their own view that doesn’t cause disruption to the product. Meaning when they move a task on their board, it will also be updated on the “main” board view.
Sure!
We have similar issues and I've been working to try and figure out the best way to work with it mostly.
In general I like a single backlog per product group (so unless something is a separate product or a shared service for multiple products, it is associated to that one backlog). If the company small enough or you have only one or 2 products then a single backlog for everything should also work well.
Jira was not structured for Agile however they are catching up...I would go with agile central or similar products build for an agile environment..yes a board for a product and a running backlog...
Mentor
Agreed on having a backlog per product. One thing I’ve recently been testing out to get the cross-product or “program” level view of work and roadmap is Jira Align.
It’s an Atlassian tool (they bought I think AgileCraft, which became Align) and sorta sits on top of different Jiras to pull a single view. It is a separate tool with its own learning curve, but if people are worried about losing the combined view, it could solve that.
How about switching to Aha! for product and using JIRA for dev + qa + release mgr?
Wow, I have a similar problem and this is all super helpful advice.
You can do a lot in Jira with labels, components, teams etc. If you tag items right and set up boards properly you can share one project but it isn't hard for teams to focus on their own stuff. If you share a project this way then other teams can peruse each others' backlogs easily.
I would go with a project for every product, if your product is long standing and you plan on making modifications. I would separate those modifications or enhancements into initiatives and then break then down into epics then stories. If you have several different products that you are launching that may be smaller and have more concise timeframes I would use the initiative feature to split your work up and link the epics and stories to that for traceability