What Is Agile Marketing? - YouTube - 0 views
What is Agile Marketing? - 0 views
Agile Marketing Manifesto - 0 views
Case Studies in Agile Marketing - 0 views
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...
http://www.agilemarketing.net/GettingStartedWithAgileMarketing.pdf - 0 views
Managing WIP isn't the same as Limiting WIP: Part 1 - 0 views
-
To determine the truth of this we only need to look at the feature sets of the popular tools for managing eXtreme Programming and Scrum such as Rally, VersionOne, ScrumWorks, Mingle and very new tools like Borland Team Focus, to discover that not a single one of these tools allows you to set an explicit WIP limit. None of them provide a pull signal to start new work. Very few of them are even capable of reporting the quantity of work-in-progress.
-
s we learned more about the value of managing WIP, we introduced concepts to encourage and enable it, such as the use of Cumulative Flow Diagrams (a.k.a. Burn Up charts)
-
Agile teams encountering an impediment would generally mark a story as blocked and go on to another one
- ...2 more annotations...
Tailor your Message To Gain Support for your Agile Initiative | Enabling Agility - 0 views
-
Connect Agile’s Benefits to your Company’s Priorities
-
aying that Agile is “better, faster, cheaper” may not be enough to cause a company to be willing to go through the often-painful process of cultural and process change. You could implement Agile, but you could also try Six Sigma or Lean. Saying that Agile is a general get-better remedy puts it in line with many other get-better methods.
-
f they don’t see a meaningful update from us, at least once a quarter, we’re going to get kicked out of the game. We’ve all acknowledged that as we’ve gotten bigger, our processes have become more cumbersome and now is the time to do something about it. Agile will give us the ability to regain that rapid pace of delivering innovations to market that we were know for in our early days.”
- ...21 more annotations...
Growth Facilitator role on an OpenAgile team | Agile Advice - Working With Agile Method... - 0 views
-
The responsibility of the Growth Facilitator is about more than simply prioritizing New Work goals and tasks. I see the role as contributing to the organizational culture, and helping to build the business in a sustainable way.
-
As Growth Facilitator, I am also responsible for guiding the team toward delivering greater value for our stakeholders. At Berteig Consulting, our stakeholders don’t just include the company’s owners. Our stakeholders include a wide range of groups, including customers, suppliers, employees, and our families, all without whose support nothing we do would be possible. Delivering value to our stakeholders requires that we keep them in mind when we commit to our tasks each week.
-
When I first started, I made goals that were broad, saying for example “to take care of our clients” or “to work at a sustainable pace.”
- ...2 more annotations...
Company-Wide Business Agility and the Soviets - 0 views
-
Tom Grant, a Forrester analyst who covers agile and product management, brought early results of his research on business agility to P-Camp. He has divided technology companies into An agile "vanguard" implementing first-wave improvements in their software development models, and Agile "transformation" companies making broad corporate-wide improvements in understanding customers and cross-departmental coordination.
-
"the end of Soviet-style development." He reminded us that Soviet five-year plans had little to do with the reality of hungry Russians and empty store shelves. In the same vein, technology companies with top-down command-and-control waterfalls tend to be unresponsive and overly optimistic. They often lack good market-sensing mechanisms or useful bottoms-up development metrics, so they routinely deliver unexciting products later than planned.