Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I need a lightweight issue tracker for a new project, with about 5 people on the project. Any recommendation? I read the two other threads on that topic, but it didn't seem satisfactory. I don't need to integrate with git. I just need something super simple, and very, very easy to setup, like a scrum board in the computer (other teams here have physical scream boards). I'm about to roll out an Excel spreadsheet in a shared directory on my Linux box...
I recommend a github account. Make a repo there and track issues using the native github issues that come with each git repository. Then use www.huboard.com to add an extremely lightweight agile/kanban view of your issues. It's easy to set up, but works well. Very simple and lightweight, and you can customize your kanban board view in huboard easily.
If you have a .edu email address github is free, and if not you can get an account that supports five commiters for only $7/month. Well worth it for the awesome infrastrucure.
Jira is nice, but it costs a little bit of money. If you're cash-strapped, you may want to consider Trac. It provides a lot of the same functionality as Jira, but there is no cost associated with it. However, if you decide you want to use a plugin to specifically track your project using Scrum and Kanban, then for your team size Jira/Greenhopper will be much less expensive than the Trac/Agilo combination. Additionally, the Jira University has a number of online-courses on how to use Jira and the Greenhopper plugin that is very inexpensive.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
We are a small development team of 3. We are responsible for the design, development, test, and publish of each software application. We also provide software support, and deal with any issues the users may have, as well as bug fixing.
At the moment, each developer is solely responsible for seeing a project through from start to finish. So they will discuss with the client the requirements for the software. They will plan, design, and develop the software (both front-end and back-end). And they are responsible for testing and bug fixing.
Is this a development process that is recommended or should each developer be designated a number of tasks on each project?
I have been thinking of applying SCRUM principles to our development process but not sure how effective they would be. From what we do I gether that we are already working in an agile methodology with short iterations, and requirement discussions with the client?
Would you recommend SCRUM for our environment? How do other small teams operate?
It depends what is your purpose: implementing Agile just because it is the newest 'fashion' might prove to be very costly for your existing business.
In my experience (almost 15 years, now) it is better to implement Agile all around the company, not only at Tech level (or DevOps as they are now calling it).
If you implement any Agile method in a development environment than you simply get a bit more efficiency in that environment, only! A coder can not write more than that number of lines a day. Than, because the rest of the business is still at 'waterfall' your development side becomes a bottleneck by having to lag because of the rest...
In your particular case, perhaps it would be a good idea to get together with the developers and ask them: Agile or status quo? Once ALL of you agree for Agile than just go for it - first do it by the book and after a few sprints just start adapting what you need to your given situation. Perhaps a bit of pair-programming, a bit of cross-collaboration etc At the end of the day you are only three people: how difficult can it be to obtain consensus? funny
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
We are using this server for almost a year now.
Last forum post seen in November, 2011.
Last server version released 28/03/12.
Just wondering if anyone knows whats happening inside the company?
Should we expect something or should we start looking for alternatives?
I did what you did not do: using email to ask the question to the people able to answer.
And they replied that:
the forum was closed because they could not cope with the amount of accounts created daily to publish junk
the next version will be the most important ever made for G-Wan, with new features like a caching reverse proxy and an elastic load-balancer as well as system replacements like a wait-free memory allocator.
With regard to such developments, a 3-month period without publishing releases sounds reasonable.
More reasonable than assuming that such an 'inactivity period' means that "the project is dead".
Would you say that for other Web servers like Apache which have much larger release cycles?
You should always be expecting something from G-WAN. It's a great piece of software. Here's the other thing too: G-WAN was expertly engineered. That doesn't mean that there are no bugs in it, or that features can't be implemented, but G-WAN is incredibly tight.
It has lean code, it does what it supposed to do, very well, and it is built for the developer to add in the functionality that hasn't been put in there yet.
That's the beauty of it, or one facet of the beauty.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have nearly finished a free spellchecker library for Windows Mobile, and there are a few great forums around (both for developers and end-users), such as XDA, where you can promote your creations for Windows Mobile.
However, I have been thinking that I'd like to make a version of my library available for Windows desktop developers as well. Once I have finished the same, I'd like to distribute and promote it to get feedback, bug reports, and suggestions.
Are there good developer forums for promoting and distributing applications or libraries in this way?
You might want to consider writing an introductory review of your own library, and publish it on sites such as codeguru.com or codeproject.com. You could also use blogs of popular sites such as ddj.com to promote your library.
On the other hand, one very simple thing to do would be to set up a sourceforge project for your library (if it's open source) and then use their facilities for all these purposes. Specifically, you can easily use freshmeat.net to make your library more widely known.
You will need a certain minimum infrastructure (forum/mailing list, issue tracker and possibly source code management) in order to provide a place for your users to easily monitor or possibly even participate actively in your project.
A simple homepage and yahoo list might very well suffice, though.
Also, looking into available spell checking libraries in general, you will probably want to highlight the major differences between your implementation/project and more established ones such as for example GNU aspell or hunspell.
So, do make sure to do some research in order to get to know related projects.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I am investigating the feasibility of setting up a discussion forum / message board in my company to enable knowledge sharing etc.
What are the steps involved in implementing such a solution?
I would definitely recommend a Wiki - we've used Mindtouch internally for a number of years and have also posted all of our documentation externally on a wiki.
The steps will depend on what technology you already have in place and what kind of shop you are. If you have SharePoint (WSS 3.0 or MOSS 2007), then you already have blog, wiki and discussion group functionality built in. Not the best in the world, but it's there.
A shop that uses more open source tools is less likely to find SharePoint compelling. ;-)
Instead of (or maybe in addition to) a discussion forum, I would recommend a wiki server. This way you can have different howtos, lists, documentation, etc available and the important things will tend to stay up to date. We have one in our department and it is quite useful (if only people would log in when editing...).
I was not involved in setting it up, so I cannot give any details on that, but it is based on mediawiki.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
If anyone is trying to do agile, i am trying to figure out a way to use JIRA / Greenhopper for this. We are a global dev team so the distributed nature is crucial here.
We were initially using Scrumworks but the team complained that they had duplicate information in JIRA and scrumworks all the time and thought it was redundant.
We got Greenhopper and thought that would solve our problems but the problems that i have with this are:
No User story concept in JIRA
Greenhopper too "task" focused without aggregation at the user story level.
Has anyone successfully done this in JIRA or should we look at moving back to other tools like scrumworks and just use JIRA for bugs raised by our support team.
You can add your own Issue types in JIRA.
Just add a type called User Story.
Then make sure to enable your sub-tasks feature in JIRA.
You will then be able to explode your stories int multiple Subtasks.
The integration of the subtasks is pretty nice if you reuse the Ranking feature.
See: http://www.greenpeppersoftware.com/confluence/display/GH/PLANNING+BOARD#PLANNINGBOARD-ordering
You will then be able to
1) Estimate your Stories in Story points
2) Prioritize your issues (with the ranking field)
3) Explode your stories in multiple subtasks that you will estimate in hours.
You should post your questions on the GreenHopper forum, might have more and quicker answers. http://www.greenpeppersoftware.com/site/forums/list.page
Cheers,
I'm using Jira 4.3 and Greenhopper and it supports user stories out of the box. There also support for Epics and Themes but you have to do a bit of configuring. Likely this built in functionality was added after the date of the original question.
You might also try using an Agile Lifecycle Management product such as Rally, www.rallydev.com. Rally is built from the ground up to support any agile process and create comprehensive reports across teams. Check it out.
Try Mingle - this has a great integration with Jira allowing software dev teams (using Mingle) and support teams (using Jira) to work the way they want.