I am looking for project planing support in JIRA. An upcoming project contains different work streams which can be quite independent of each other. For each work stream the corresponded tickets will be stored in JIRA.
Assuming that for each ticket the effort estimation in days is derived. I am looking for the following visualization:
WS1: Ticket_1_1 Ticket_1_2 Ticket_1_3 ...
WS2: Ticket_2_1 Ticket_2_2 Ticket_2_3 ...
....
WSN: Ticket_N_1 Ticket_N_2 Ticket_N_3 ...
Accompanied by the calendar time axis.
The representation will be used for the definition of implementation order and challenging of project timelines (or ticket descoping)
Does JIRA support such or similar visualizations (may be through plugins)?
Could you please provide some suitable ideas?
Best,
you may try Portfolio for Jira.
Example: https://www.teamlead.ru/pages/viewpage.action?pageId=18514705
HTH
JIRA is available for rich visualization and reporting functions as it widely uses in the industry. JIRA dashboards and visual boards make better sense in the data-driven approaches. This may help you to have a better discussion on JIRA reportings HERE.
Let me recommend some sort of tools you may be helped in this context. ZOHO , ASANA
Related
JIRA QUESTION!!! What's the best plug-in extension for Jira that will help multiple people collaboratively score features(Jira issues) in order to prioritize them? Any recommendations would be SUPER SUPER SUPER appreciated.
We looked into product board but it's not really meant for collaborative scoring. We want multiple people to be able to collaboratively score at the same time like Google Sheets, but just something embedded within the Jira environment.
I seem to recall a Jira Poker plugin from Spartez. They are reputable.
Sourcegraph- this site help me find usage of some of the libraries and usage examples provided by others, where official documentation of the libraries would go only so far. This has been incredibly valuable to me as a developer.
I'd like to see how other developers have used some APIs. We are working on a really huge team. Of course there are all sorts of permissions restrictions for multiple projects. However, most of the code is open. It really is a valuable asset to people like me.
TFS is a source control provider, I think it should also have something inside like sourcegraph. My question is- What's the best way to do this in TFS?
Suggest you to upgrade your TFS to TFS2017. This new release includes our most recent feature innovations and improvements. One of important update is code serach.
Code Search
Code Search provides fast, flexible, and accurate search across all your code. As your codebase expands and is divided across multiple projects and repositories, finding what you need becomes increasingly difficult. To maximize cross-team collaboration and code sharing, Code Search can quickly and efficiently locate relevant information across all your projects.
From discovering examples of an API's implementation, browsing its definition, to searching for error text, Code Search delivers a one-stop solution for all your code exploration and troubleshooting needs.
Code Search offers:
Search across one or more projects
Semantic Ranking
Rich filtering
Code collaboration
For details, see Search across all your code.
Sourcegraph now supports full-regex search across all code and is now deployable as a single Docker image (https://about.sourcegraph.com/docs) and indexes any Git-based code host.
I have a project with 4 teams handling different parts of a fairly large web based system. What would be the best way of handling this in Jira and Jira Agile?
One project and board per team or is there another way of organizing this in Jira Agile?
Read about using components but since I'm fairly new to Jira Agile I don't know how to do that.
If many team are working on different part of the same system, I suggest you create only one project. From my experience there is a lot of chance you will want to move 'items' from one team to another or link two items that are related but not handle by the same team.
Like previous posts mentioned, GreenHopper is just an (agile) plugin that help you manage items in JIRA, allowing to display and manage them in different ways. The plugins is especially useful if your are following a development process like Scrum.
With the last version of the tools I was able to easily share a single 'backlog' of work to do between multiple teams and then 'assign' items to a specific team when it's time to work on it. When planning for the next Sprint, for example.
Of course having a clear view of your process is key.
I think you are confused about a few things, which is understandable for somebody new to the tool.
Jira is the software you are using and Greenhopper is an external company that produces plugins for it, mainly the Agile plugin. Components are within Jira and they are simply a way you can categorize your issues. I suggest you find a tutorial video on jira to introduce you better to the tool.
Now, again, these are just tools. They don't dictate how you should work. Jira is very flexible that way so you can do Agile, Scrum, Kanban or whatever methodology you want within it.
You need to first decide what methodology/process you will adopt. Basically, how will you guys work?
Are all the teams working in sprints? Do they have the same deadlines? Are the stories-issues parts of a whole or can each team deliver a full feature on it's own?
For example, if one team is infrastructure, one is UI and one is DB, their parts will likely come together to make a "whole" feature, that is complete and tested.
Another example is if team A is doing a Reporting Module and team B is doing a Login module, their features aren't usually related and they can work separately.
So basically, you can't ask anybody here to give you the straight answer. Stop focusing on the tool and understand how you will work and what makes sense for you.
And remember: agile is trial and error. Try something and if it doesn't work, adapt.
I am starting a game design project with a group of three other students. We would like to use some open source hosting service for version control, a wiki, etc. I have looked at threads like these (https://stackoverflow.com/questions/10490/best-open-source-project-hosting-site, https://stackoverflow.com/questions/29736/what-open-source-hosting-service-should-i-use, http://en.wikipedia.org/wiki/Comparison_of_open_source_software_hosting_facilities) but am still not sure which is best for our situation. Those threads seem to focus more on large scale, long term open source projects, whereas my group will be small and working together for a relatively short time.
Here are my constraints:
group of 4-5 people
10+ hours per week per person spent working on this project until May 2010
Language/framework: C# XNA
IDE: Visual Studio 2008
project will be no bigger than 100 mb
Features that would be nice to have:
Wiki
Milestone tracking
Issue/bug tracking
Code reviews
Document hosting (like the game manual, design spec, etc)
I'm thinking CodePlex would be nice because of its support for Visual Studio. I've had a positive experience with CodePlex in the past for a tiny project. However, Assembla has a nice UI, and its time tracking feature/linking tickets to SVN commits seems like it could be really helpful. (The time tracking in particular appeals to me, because if certain group members are slacking it could show through here.)
Google Code has been praised by many in the aforementioned threads, and everyone in my group has a Google account.
Also, I'm not sure which license we should pick for our project.
Codeplex already has lots of XNA related projects being hosted on it. One of the great things about codeplex is that you can choose from a large number of source control clients. It supports the TFS client, SVN, and mercurial. So from a flexibility perspective, it's very very simple.
From a license perspective ... well, you didn't really give enough information about what your goals are. Do you want a license like GPL, which ensures that your code can't be used in a closed source project dodwnstream? Do you not really care who does what?
Personally, for the open source projects I've hosted on codeplex, I prefer the mozilla public license. It basically says the code is as is, and you can do whatever you want with it, open or closed.
Google Code has been praised by many
in the aforementioned threads, and
everyone in my group has a Google
account.
I think this coupled with easy usage of Docs/Groups/etc. and what not for things you dont nesscearily want public as well as group integration, all with interfaces that the entire team is most likely already used to working with, makes it a logical choice unless there are some features better fulfilled by another service in your opinion. In not nessecarily singing the normal paraises of google here - it just seems like a very pragmatic no fuss solution.
I finally was able to complete the installation of TFS and started the creation of my first team project which introduced me to the process template.
After following to the link to Microsoft's site for process template information I was inundated with new information to consider. What templates have all of you had experience with that either worked out very well for you or were more of a stumbling block to the project? What were the biggest advantages and disadvantages you've encountered?
Some information about my project, I'm the lead developer for a small company and will be using TFS/VSTS to create an intranet portal to consolidate the end users day to day and increase automation to enhance productivity etc. It's entirely new development taking advantage of C#, ASP.NET and SQL Server 2008.
Ideally I'd like to take advantage of features to enhance collaboration with the stake holders to help add desired features and to track the status of development and offer feedback etc. I was also looking to take advantage of JetBrain's TeamCity for my TFS so if any specific template / software really adds cohesion between TFS, TeamCity, Developers, and Stakeholders that would be ideally what I'm interested in.
Are you already using a software development process like scrum? If yes you can try this Team Process Template over here.
How large is your project team and the project? Microsoft has published one of it's internal Process Templates (MPT) over here. You can get some guidiance and inspiration from this template.
As tangurena mentioned. People use the standard templates, change the bug a bit and store some documents there. I would recommend to keep the process 'light' as well.
However the process template isn't all.
Here are some ideas what I would do (in your case):
Create some high order workitems (features/stories) which stakeholdes can create (constraints and TFS user groups are your friend). They can then access their requested features via the TFS Work Item Web Access. That way you don't need a CAL for them
Create some reports which show planned work accodring to releases.
Setup the build automation and create Reports (a.k.a. Release Notes) from your workitems according to the builds.
What were the biggest advantages and disadvantages you've encountered?
Imho the biggest disadvantage is that you start believing that the template is your silver bullet. It's not, it's your starting point.
The TFS ecosystem offers you alot opportunities to create own bits of software that fit your needs. Just check out the TFS API.
Here is another nice agile-based template (original is on SSW, but you have to get around a login wall).
This template helps enhance cohesion between developers, managers, and other stakeholders by including more robust support for project process (documentation, reviews, &c., &c.). For example, there are types built in for process elements like release plans.
In general terms, I'd favour as small a process as you can manage. The more states, the more fields you have, the more likely the information in them is just plain wrong.
We're running with our own version on the Agile template. Most of what we did to it was delete stuff.
You can use the TFS API to log builds into the database, which should enable you to bridge TeamCity and TFS. Other than that, I'd probably just go with the web interface that comes with TFS, I don't think you need third party software for this.
K.I.S.S.! I created a custom work item based off the Agile one. And thats it, just one work item. There is a "System Severity" that IT uses and a "Business Priority" that the client/customer uses. There is also a "Request Type". With those three along with the built in Area and Iteration the entire team, including the clients can query the work items to get only the items they care about for the release they are concerned with (or all of them regardless of the release).
I did not modify the state machine much at all. This left us with something that is very flexible for everyone. Everything from blue sky requests to the mundane content/visual bugs can be logged there.
The client uses TFS Web Access (unlimited CAL) and the devs (me and 1 other) use VS. At my last job I created the same setup, the dev team was a team of 5 and it worked even better there! I was dev lead there as well and technical PM.
The biggest advantage was having a very flexible system for everyone, when using 1 work item type for everything. The disadvantage would be a learning curve for the client, but once they knew how to use it most like it. A suggestion would be to look into cheaper tools out there for a similar implementation, but, our .edu discount with MS cant be beat.
I would have to say that you must identify the system you will use for your company's SDLC first. The process template is merely a tool and without a good understanding of the underlying process it will not help and can make things more difficult. User adoption is crucial to the success of the SDLC and process template.
We use Scrum for Team System. We chose this due to our experience with Scrum as an SDLC methodology. There are several excellent books and articles on the web to help you get up to speed. Scrum will tie together the business stakeholders into the process.
In our system the Product Manager is in total charge of Product Backlog Items and works with myself and the CTO to prioritize them into Sprint Backlog Items.
The only change we have made to the process template was to add a "Failed Test" state and corresponding workflow.
It might not be the best template for you but I still wanted to mention it here: XP for Team System. It is basically a simplified version of MSF for Agile Software Development:
[...] it removes some of the setup tasks that an XP project will probably not want to undertake and changes the Work Item Type name Scenario to Story.