Good attempt.  I am sick and tired of version1 and thought of perhaps
some OSS had done it earlier. And I am glad some folks from Catmando
did it.  Here are my wishlist.


*  There should be a feature for defects where a project owner or QA
or any of the team lead can create defects. It gives agile teams to
plan and track fixes as separate asset. The test should remain
consistent to the working hours everyday.

* The estimation hrs of each task in the backlogs should not go in
seldom, or based on an individual (may it be product owner or scrum
master or tech lead). I prefer consensus-based estimation approach.
As I take ownership of couple of projects, I try to make sure my
estimation meets my team expectation (at least in majority). To make
job easy, We play poker card deck.
Think about this approach where all have rights to estimate the task
in the early stage of Sprint Planning and you pick up the average
estimation of each given task.

* Sprint Tracking is important. If a product owner or manager wants to
track the current progress in summary or indepth then this should
reflects the both side of the true state of the sprint.  For example,
I want to see member progress Individually (or group or team)
remaining effort or both the effort completed which represents current
state of sprint at any given datetime in the burn down chart or any.

* Is there any option to move backlog items or defects from one sprint
to another?  Sometime we split a partially completed backlog item and
move the remaining one to next sprint and How do we close all
completed workitems?

* At the end of each sprint, we have review often brings surprises.
Here retrospectives logs comes in place. It should not limited to one
entry. A scrum master should able to create manage multiple
retrospectives on basis of the last sprint review. Also it should
allows us to view full details of any retrospective at any given
point.

* make design it modular & extensible.

* Try to improve UI. Use some good JS framework and follow consistent
design models.


On Jun 30, 4:24 pm, "[email protected]"
<[email protected]> wrote:
> Dear all,
>
> FOSS Nepal is very active community and it is great to see people
> calling for help and some one response in very short time.
>
> Notification about some new open source tools and other development is
> also very helpful to keep myself up to date about open source
> development.
>
> Today i want to share about my project saralScrum. It is project
> management tool based on Scrum methodology. It is developed using PHP
> and MySQL and Symfony framework. It is opensource and totally free. It
> will be very helpful for any project manager.
>
> Scrum is one of the best methodology among agile project management
> methods. Its real strength is to make all the development and problems
> visible to all. It is iterative and incremental based so Scrum
> believes in delivering working software in iteration with most
> important feature first. So Scrum insures your customer gets product
> with high value.
>
> Some features of saralScrum are as follows:
> 1) Project definition
> 2) Product backlog definition
> 3) Release, Sprint definition
> 4) Sprint backlog definition
> 5) Release and Sprint burndown chart creation
> 6) Dashboard to get summary of project status
> 7) Chat for daily meetings
> 8) Project member management with privilege definition
>
> Yesterday i have release v0.3.3.
>
> Anyone can download it fromhttp://collaborate.d2labs.org/projects/saralscrum/
>
> I welcome your suggestion and comments.
>
> Best regards,
> Ritesh M. Tamrakar
--~--~---------~--~----~------------~-------~--~----~
FOSS Nepal mailing list: [email protected]
http://groups.google.com/group/foss-nepal
To unsubscribe, e-mail: [email protected]

Community website: http://www.fossnepal.org/
-~----------~----~----~----~------~----~------~--~---

Reply via email to