Dashboard - Stormz - 0 views
A Checklist for a Distributed Retrospective › Marc Löffler - Scrum, Kanban an... - 0 views
Negotiation Tactics - 0 views
-
In negotiation, there are many tactics that you may meet or use. They can be fair, foul or something in between, depending on the competitive or collaborative style of the people involved and the seriousness of the outcomes.
-
Behavior Labeling
-
Cards on the Table: State your case, clearly and completely.
- ...3 more annotations...
InfoQ: Ensuring Success for Self Organizing Teams - 0 views
-
Helicopter Managers – who step in too soon to rescue thereby depriving the team to think and solve problems together.
-
Absentee Managers – who would not step in at all irrespective of whether the team has all the necessary skills to tackle the problem.
-
If the team has sufficient skills to solve the problem then give them space else ask questions to help them get unstuck. This would help in building the skills eventually.
- ...7 more annotations...
Agile Resources: Velocity | VersionOne - 0 views
-
Does maximum velocity mean maximum productivity? Absolutely not. In an attempt to maximize velocity, a team may in fact achieve the opposite. If asked to maximize velocity, a team may skimp on unit or acceptance testing, reduce customer collaboration, skip fixing bugs, minimize refactoring, or many other key benefits of the various Agile development practices. While potentially offering short-term improvement (if you can call it that), there will be a negative long-term impact. The goal is not maximized velocity, but rather optimal velocity over time, which takes into account many factors including the quality of the end product.
Kanban development oversimplified: a simple explanation of how Kanban adds to the ever-... - 0 views
-
It’s a lot easier to estimate a story that’s small — which can lead to more accurate estimates, and better predictability.
-
It’s easier to plan with smaller stories. With big stories — stories that might take weeks for a developer to implement — it becomes difficult to plan a development time-box — particularly when the iterations are only a couple of weeks. It seems that only a couple stories fit — and there’s often room for half a story — but how do you build half a story? Splitting them into smaller stories makes it easier to plan those time-boxes.
-
Shrinking stories forces earlier elaboration and decision-making. Where product owners could write their stories fairly generally and consider many of the details later, now breaking them down into smaller stories forces more thinking earlier in a planning lifecycle.
- ...36 more annotations...
EE Times - Using agile methods in medical device development - 0 views
-
FDA and other regulatory agencies fundamentally want to see that your product has safety in mind. To do so, they require complete traceability through the hardware and software. There is even a fairly new standard, IEC 62304, adopted worldwide that is wholly focused on software traceability from requirements through architecture to tests.
-
Medical devices companies are going primarily agile to respond to change and effectively manage technical complexity by collaboratively building solutions with their partners and customers to ultimately deliver what the customer wants before the competition does.
-
demo the new functionality created after each iteration to your customers, using web-based meets. Using these tools enables you to get immediate feedback from your customers throughout the project. Continuous customer feedback reduces the risk of building the wrong solution. The fact is in most cases you can’t make the release cycle more frequent since it includes giving tests to regulatory agencies. This is a tedious process that makes sure the device is safe. Doing the whole release cycle more frequently can be way too time consuming.
- ...3 more annotations...
Ambler - Doing RFPs the Agile way - 0 views
-
RFPs the Agile Way -- or -- Fear and Loathing in the Procurement Department
InfoQ: Comparing Kanban To Scrum - 1 views
-
Scrum in a nutshell Split your organization into small, cross-functional, self-organizing teams. Split your work into a list of small, concrete deliverables. Assign someone to be responsible for that list and to sort the list by priority. The implementation team estimates the relative size of each item. Split time into short fixed-length iterations (usually 1 – 4 weeks), with potentially shippable code demonstrated after each iteration. Optimize the release plan and update priorities in collaboration with the customer, based on insights gained by inspecting the release after each iteration. Optimize the process by having a retrospective after each iteration. For more details check out “Scrum and XP from the Trenches”. The book is a free read online. I know the author, he’s a nice guy :o) http://www.crisp.se/ScrumAndXpFromTheTrenches.html Kanban in a nutshell Visualize the workflow Split the work into pieces, write each item on a card and put on the wall Use named columns to illustrate where each item is in the workflow Limit WIP (work in progress) – assign explicit limits to how many items may be in progress at each workflow state. Measure the lead time (average time to complete one item, sometimes called “cycle time”), optimize the process to make lead time as small and predictable as possible.
piplanning app - 0 views
1 - 15 of 15
Showing 20▼ items per page