30

Which one is better? The one that works better for the team. That is the entire point of Scrum. Enable your teams to organize around practices and tools that work for them, and stay out of the way. It really doesn't matter what your Agile coaches like and don't like. Their opinion can be used as a basis in your team, but the bottom line is to use what works....


18

In situations like this two important rules are in conflict: don't lie to the client don't look bad in the eye of the client Based on my experience, clients appreciate the outcome of the first rule, so if you are honest and tell them about the background of the issues, they'll most probably understand them (of course, there are client, who will try to use ...


16

"Feature Velocity" vs. Capacity-Based Scheduling Pivotal Labs is making a marketing decision with this design choice. By addressing themselves to "business value" as the key metric, they are implicitly discounting the importance of tracking team capacity or project scheduling in a broader sense. Another way to look at this is that they are trying to sell a ...


14

Why Agile Practices Generally Favor Face-to-Face Solutions [A]fter speaking with Agile coaches it appears they don't like this virtual solution because it breaks the real interactions promoted by the Scrum framework. According to one Wikipedia entry, 2/3 of all communication is non-verbal. In an agile context, this means that in-person interaction ...


14

I know this thread is a little old now, but as a developer at Pivotal, I don't completely agree with any of the existing answers. The philosophy behind not estimating bugs isn't that bux fixing doesn't deliver business value, it's that introducing a defect into the app and then fixing it does not represent net forward momentum. For example, let's imagine ...


13

I won't say that it is all about communication, but I think a large portion of the problem you see can be contributed to communications that could be improved. I work in the same field, and I've seen this behavior from many clients in different industries. What took me a long time to understand was that the way I initially present estimates can have a huge ...


12

I support Zsolt approach, adding one suggestion when planning the way to deliver this information to the users: Before the fix: What caused (a misconfiguration on the application, a typo?) Why it was caused (a last minute requirement change?) why it wasn't noticed (lack of proper testing?) After the fix: Is there any potential similar problem somewhere ...


11

TL;DR Don't think "time tracking." Think "cycle time" instead. Kanban Should Measure Cycle Time Generally, Kanban is not about measuring "activities" at a granular level; it is about measuring cycle time for a pull through the entire system. There is legitimate debate about whether this time should include lead time (e.g. time spent in the ice box) or ...


11

The point of having scrums is to facilitate intra-team communications. From that point, having a physical board is beneficial because it forces people to be in the same room and communicate face-to-face. Remember that something like 75-80% of communication is composed on non-verbal cues, so if you are trying to do things virtually when you don't have to you ...


10

Kanban certifications are definitely not as well established as Scrum training/ certifications. But they certainly are available. The Lean Kanban University, with active involvement of/ direction by 'Kanban Method for Software' pioneer David J Anderson, has been issuing 2 kinds of certifications - AKT - Accredited Kanban Trainer - and KCP - Kanban Coaching ...


10

Your Capacity Planning and Prioritization Processes Need Re-Engineering You appear to be attempting to solve the wrong problem by treating this as an individual-availability issue. This is most likely because you have a weirdly-matrixed organization that isn't based around project teams or team capacity planning, but apparently based on the notoriously ...


9

Start by implementing the process, not software. Are you all located in the same space? Go old school and use notecards and post-its. That is how we started our iterative dev team off, and it works quite nicely. If you must use software... How big is your team? Mingle from Thoughtworks is good, but expensive ($400 a user annually). It is free for <5 ...


8

Based on my own experience I would recommend Jira or Mantis. Jira is a paying solution but is by far the best I have used. It has agile plugins like greenhopper, ideal for visualising the workflow on cards. A free solution that might work: Mantis is a open source bug tracking solution that works very well.


8

Transparency and Root-Cause Analysis If you're running an agile shop, transparency should be a key objective. Even in more traditional PM approaches, it's usually a bad idea to sweep issues under the rug. Invisible issues can't be managed by stakeholders or the project management process, so one should always strive for transparency. Address Process; Don't ...


7

I would recommend https://trello.com/ Have been using it for tracking activities of my team ( size - 10 testers) It is straightforward, not too clutter or complexity , is free and should tick the boxes from your question


7

You can plan a project without a software tracking tool, you can't plan a project without communication. The tools is just that, a tool. You use it to help you get what you want done. A hammer won't build a house, but it will make building the house a lot easier (using rocks to pound in nails is hard on the hand). And as Zsolt says, tracking tools do ...


7

The way we solved this problem was to use Scrum for Trello Chrome extension. Yes, that means that anyone viewing Trello as a Kanban tool needs to do so via Chrome, but in our group that wasn't a problem -- your mileage may vary. At the card level, the extension adds the ability to assign point value to the card: At the list level, the extension shows the ...


7

Skips the Tools; Build a Process You describe your current process like this: Get order, a lot of communication with files that specify the details, delivery, more communication on setup and support. Then it can be years and the software needs to be updated according to new specifications and the communication starts again before a new delivery. While ...


7

You should take a look at Jira Issue Collector. An excerpt from its docs: Need to capture feedback on your website or web application? Want to make it easy for end users to directly create bugs so your developers can act on them? If you develop web-applications or web sites, the JIRA Issue Collector is the best way to turn your customers' and users' ...


7

First: Document Your Process We don't do shopping questions here on PMSE, but we're all about process. The correct way to comparison shop for any tool is to document your actual work-flows and project processes, and then find a tool that supports what you are actually doing. Write down how your team does things right now. If your project is just forming, ...


7

You should estimate bugs and non-functional requirements I am not familiar with Pivotal Tracker. However, looks like your question is more general: Should I not be estimating bugs? Should I not be estimating technical debt or non-functional requirements? I think this is what you are referring to as "chore". In my opinion, you should be estimating these. ...


7

This is about span of control. And there are rules of thumb to help an organization decide when it is time to put in a layer of control. Of course, there are competing and contradicting schools of thought on this. You need to research the benefits, costs, and risks of different approaches to see what fits best in your organization for this project at this ...


6

When you think about it a bug tracker is nothing but simple task management application with (a simple) workflow attached to every item. From this perspective it doesn't really matter whether a work item is a software bug, a task to perform or anything else. It means that you should be able to use bug trackers to achieve the goal you define. I was ...


6

Certifications are (Just) Sales Tools [D]o you find this kind of certificates any useful? Do you think, that candidate with such certificates (assuming the same achievements and experience) have any advantage over the others? While I won't address the state of available certifications (as I consider that a searchable question with non-canonical answers) ...


5

I recommend something simple we do at our weekly resource planning meetings. We use the white board in a conference room to hand-draw charts, similar to what you might see in project management and scheduling software. Then next to each project we annotate the charts with each team member's tasks for the next few weeks. Sometimes, to improve visibility and ...


5

In my organisation we are using SharePoint Enterprise 2010 to manage projects by setting up workflows. This is a MOSS as Outlook which can be perfectly integrated and synchronised with the relevant project team. With SharePoint we produce and manage Dashboards, Metrics, Risks Logs, etc... that are used not only to communicate the status of the project to ...


5

I like whiteboards. Corkboards are nearly as good, but harder to reflect changes in process on, IMO. While pinned index cards don't fall off as often as stickies, if your stickies are falling off you might want to look at how long it's taking to get them off the board in the first place. I've also seen cupboard doors, table tops and windows suborned into ...


5

We do this the other way around: Requirements are handled in confluence (the wiki part of the atlassian suite). In Jira, for each requirement, one or more Epics/Userstories are created, but only for the next 2 or 3 milestone releases. Back linking from jira into confluence is done with a simple HTML link (confluence does autolinking if you cut and paste a ...


5

More than probably your task is set by default as "Fixed Units" so the initial 22 hours of work are not kept fixed. Now 217.13 days * 8 hours/day = 1737 hours (the task duration in hours) Whenever you add a new resource in "Resource names" column MS Project tries to guess what you want to do. And by default he believes you are adding a new resource with ...


5

Well based on Trac's website docs... "Component — The project module or subsystem this ticket concerns." The Trac Ticket System Hope that helps.


Only top voted, non community-wiki answers of a minimum length are eligible