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 decided that my final project for university will be a minimalistic agile project management tool. I need to find a set of features to develop. I looked at JIRA, but it has a ton of features. Which should I choose to add to my app? In your opinion, what are the most wanted feature(s) in an agile development tool?
By agile tool, do you mean a Scrum tool or a Kanban tool?
For Scrum, the minimum feature set would be:
Add stories to a backlog
Prioritise stories in the backlog
Create sprints
Allocate stories to sprints
Break stories to tasks and estimate them
Edit tasks
Generate sprint burndowns
For Kanban, the minimum feature set is:
Create a board
Customise the columns on the board
Add cards to the board
Move cards between columns
Remove/Archive cards on the board
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 4 years ago.
Improve this question
I am new to Scrum and I am trying to use it for website support and maintenance.
For website support and maintenance, we often receive small tasks, for example: replace a banner on homepage, change phone number on contact page, remove image xyz on article 123, etc... I don't know how to deal with these small tasks in Scrum.
At the moment, I create a single task in backlog, and a single Sprint for each task. Then, execute each task individually. Am I right?
In Scrum we have fixed length, repeating sprints. We bring work to the sprint, rather than creating sprints from tasks.
This is useful for a number of reasons, including:
After a while we get to know the capacity of a sprint.
We know at the start of the sprint what we will be doing and there is no change to the sprint goal during the sprint. This stability helps the team get organised.
The regular cadence helps the team get into a rhythm of planning, executing and then adapting.
Scrum isn't as effective if:
You don't have a team of 3-9 people
Work items and priorities change frequently and stable sprints are not possible
From your description, I wonder if Scrum is the best agile framework for your team.
Perhaps you might consider using Kanban?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
Is there a methodology where the process combines Scrum and Kanban and has both fixed sprint schedules and project backlog? I've heard of Scrumban and Kanplan but I'm not sure which is which.
Thanks.
Kanban is a method to visualize and improve whatever you do currently. The Kanban Method encourages you to visualize your current process on a Kanban board, establish a pull mechanism to ensure team members take up new work when that actually have capacity, and improve the flow of work thru your process.
If you are currently doing Scrum and you apply Kanban on top of it to improve your team's performance, you are doing what is popularly called Scrumban.
Kanban helps Scrum teams identify and resolve bottlenecks in their current processes, using concepts such as WIP limits (to reduce multitasking) and classes of Service to deal with the variations in demand (the different types of work a software team usually does, such as new features, break-fixes, etc.) and make commitments to their product owners and other stakeholders based on their real capacity to deliver work.
In this process, Scrum teams may often move towards a 'sprint-less' delivery (just do releases on a regular cadence), while improving the frequency with which they deliver quality software. If they do so, many teams call that thenKanban process. However, that is not a necessary step at all. Team's can simply continue with Scrumban.
If you'd like to learn more about this, you can read up here - http://www.digite.com/Kanban-guide/what-is-scrumban
Hope this helps!
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 6 years ago.
Improve this question
In my agile development course, after gathering user requirements, I'm asked to write a plan (for developing an application) that is supposed to define project activities, milestones - iterations and deliverables. The plan is actually the work breakdown.
So what should the initial plan in an agile project look like? If I'm giving a plan of everything in advance (as the homework asks), isn't that the waterfall model. If each iteration in agile deals with the whole cycle of plan-do-check-act, then why do we need an initial plan?
You need an initial plan because somehow you have to decide how many people are going to work on the project and develop a budget. You can never know what your scope, time, and budget are all going to be, but generally one of these is going to be fixed. Figure out which is the most important and build a plan around that. Without this as a starting point, nobody is going to fund the project.
Build a project backlog with all of the known goals. Then pull out the biggest of the goals as key milestones. Generally, a client needs to see progress towards their desired feature set. A smart client will be prepared to adjust these as the project goes, but you can absolutely lay out a series of goals to give you targets for creating working software with each sprint.
You should read Planning Extreme Programming by Kent Beck. If you ignore the extreme part of the title you can easly adapt this to your agile methods.
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
Is it possible to or how should one use agile development processes (Scrum/XP) and write user stories in order to develop purely technical programming libraries (think Spring or a game engine for example)?
Yes, you can use agile to develop software that doesn't have a front end UI used by human users. First, because you don't have to use user stories to be agile. Even Scrum doesn't prescribe that the backlog has to be expressed in user stories. It just says there should be a backlog, it should have one order of priority and items on top of it should be small enough to fit into one sprint. They can be expressed in any way that is understandable to both the Product Owner and the team.
But, second, you can write user stories for libraries too. You just think of potential pieces of software as roles - or even create imaginary personas that could be using this library directly. "As a text editor I can call this library to encode strings in Base64" would be an off the bat example of the former technique.
To sum it all up: any type of software can be developed with agile, user stories are not key to agile - they are just one pretty useful technique frequently used by agile teams.
The same as you do for business-based requirements, except the reqs are prioritized by the API consumers/technical people?
If you're talking about Spring or Game engine, you still have a customer/product owner point of view to write your stories from..
That's you'd talk about your API, how other developers will use interfaces or what is exposed of your black-box
They are many component vendors that use Scrum to manage the development of their libraries.
I can tell you two of the StackOverflow.com sponsors are using it actively.
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 6 years ago.
Improve this question
I am taking a software development class right now and we are discussing agile methodologies. What are the most common agile methods? I need to look into several and discuss their strengths and weaknesses. Seems more useful to look into the most prominent methods.
Observations:
Scrum seems pretty popular (that is what my team used on two of my coops).
Extreme also seems to get quite a bit of buzz but I am not sure if that many people actually use it.
What does your company use and how do you like it? Does anyone use:
Agile Modeling
Agile unified process
DSDM
Essential Unified Process
Feature Driven Development
Open unified processes
Rational Unified Process
Are there other methodologies that I should investigate?
I've used SCRUM in personal projects with friends and schoolmates and my current employer uses a custom agile process that's very similar to SCRUM but with fewer meetings.
We have used Test Driven Development and Scrum.
I've been on some very successful teams which used Scrum very effectively. It really does help to keep everybody focused and constantly moving forward, and it discourages regressions.