RSS

Vaguery + agility   110

Let It Roll - CFO Magazine - May 2011 Issue - CFO.com
"Separating the three decisions has enabled the company to set targets that are more ambitious, intelligent, and motivating, says Bogsnes. As a result, the forecasts are less biased, and resource allocation is more dynamic and self-regulating. "The 'bank' is open 12 months a year, not just six weeks in the fall," he says. "By making resource decisions as late as possible instead of in an annual budget, we have better information — not just about project attractiveness but also about our capacity to fund or man new projects."

Encouraged by positive results from abandoning the budget, Statoil recently decided to abolish the calendar year as a planning tool and introduce a business- and event-driven management process in its stead."
budgeting  finance  management  planning  forecasting  agility 
june 2011 by Vaguery
Time as a Competitive Advantage | Mike Cohn's Blog - Succeeding With Agile®
"Innovation has become a fertile area in which companies seek competitive advantage today. This has served Apple well over the past decade. I don’t think innovativeness will be going away soon as a source of competitive advantage. But I do wonder whether time is running out on time as a competitive advantage. If agile and other innovations lead us to a world where all companies can deliver new products and services equally quickly, companies will need to find newer ways to differentiate themselves."
innovation  competitiveness  agility  strategy 
june 2011 by Vaguery
Software Engineering [PDF]
"…In my reflective mood, I’m wonder- ing, was its advice correct at the time, is it still relevant, and do Istill believe that metrics are a must for any suc- cessful software development effort? My answers are no, no, and no."
software-engineering  agility  software-development  metrics  what-gets-measured-gets-fudged  rescinded  on-second-thought  management-consulting  from delicious
february 2011 by Vaguery
Neural Ensemble News: Open Research Computation: a new journal for publications describing scientific software
"The goals of the journal are to promote sharing of high-quality scientific software (e.g. there must be a test suite with 100% code coverage), promote discussion of best practice in research software development, and to enable researchers to be rewarded through publication for the time spent on developing software tools for others to use."
agility  scientific-computing  software-development  open-source  journals 
december 2010 by Vaguery
Gojko Adzic » Let’s change the tune
"Until I started using Specification Workshops as the name for a collaborative meeting about acceptance tests, it was very hard to convince business users to participate. But a simple change in naming made the problem go away."
agility  agile-management  communities-of-practice  what-you-call-things-really-matters  practice  craftsmanship 
august 2010 by Vaguery
Liz Keogh's blog » What not to test
"Work out which bits of the system you know least about. Create the scenarios and have conversations around those bits of the system. You don’t have to grow the system from the beginning – you can pick any point you like! Which bits of the system make you most uncomfortable? Which bits make your stakeholders most uncomfortable?"
agility  bdd  behavior-driven-design  best-practices  advice  software-development 
august 2010 by Vaguery
2010 BLogic: Redefining Done
"A story isn't done until it is being used by real users in production and has been validated to be a useful part of a product."
agility  lean  agile-practices  project-management  progress 
august 2010 by Vaguery
Exploration Through Example
"Research programmes, even ones as successful as Newton's, eventually degenerate. A programme "is degenerating if ... (1) it does not lead to stunning new predictions (at least occasionally...); (2) if all its bold predictions are falsified; and (3) if it does not grow in steps which follow the spirit of the programme." (ibid, p. 106) (This last seems to mean avoiding the ad hoc additions mentioned above. But I think there's also a less pin-down-able sense. It would not be in the spirit of an agile method to extend itself by adding more and more examples of written process documentation.)"
Lakatos  philosophy-of-science  philosophy-of-engineering  disintermediation-in-action  agility 
july 2010 by Vaguery
TEST HEURISTICS CHEAT SHEET [pdf]
agile-practices  testing  software-development  hints  agility  best-practices 
june 2010 by Vaguery
Rhizomatic Education : Community as Curriculum @ Dave’s Educational Blog
"In the rhizomatic model of learning, curriculum is not driven by predefined inputs from experts; it is constructed and negotiated in real time by the contributions of those engaged in the learning process. This community acts as the curriculum, spontaneously shaping, constructing, and reconstructing itself and the subject of its learning in the same way that the rhizome responds to changing environmental conditions…"
education  pedagogy  generalism  agility  academic-culture  social-norms  network-culture 
may 2010 by Vaguery
How To Communicate with your Investors between Board Meetings
"Think of it this way: if having your development team work this way through sprints, why not board notes? Meeting every 6-8 weeks with no interim communication is like the waterfall software development process!"
agility  venture-capital  startups  startup-culture-must-die  entrepreneurship  advice  communication  risk-management 
may 2010 by Vaguery
Quality vs Speed? I Don’t Think So! | xProgramming.com
"Is it possible that if we keep our focus on longer term sustainability, we can still go just as fast in the short term? I believe that it is possible, and that we already have credible evidence that it is possible.

Most of us believe that over the longer term, speed is maximized by operating at a high, but not stupidly high, level of quality. The question is, what is “longer term”?"
agility  project-management  planning  quality  speech  software-development-is-not-programming 
may 2010 by Vaguery
Exploration Through Example » Blog Archive » About “Business Value”
"Quite often these teams, especially Agile teams, seem obsessively focused on “Business Value”, but that’s in the context of personal relationships. “Business Value” is a shorthand, a way of keeping conversations from going astray, of keeping people focused. It is a term that signals or reminds of other things—it is not a thing in itself.

Increasingly these days, when I hear people theorizing about Agile and Lean, they are treating “Business Value” as a thing in itself. It is treated as an end, rather than as a means. (This is in keeping with the decline of Agile as a bottom-up team-oriented insurgency.)"
agility  agilism  business-value  software-development  methodologies  cultural-norms  business-culture  figure-ground-error 
april 2010 by Vaguery
Coding Dojo Wiki: KataFizzBuzz
"Imagine the scene. You are eleven years old, and in the five minutes before the end of the lesson, your Maths teacher decides he should make his class more "fun" by introducing a "game". He explains that he is going to point at each pupil in turn and ask them to say the next number in sequence, starting from one. The "fun" part is that if the number is divisible by three, you instead say "Fizz" and if it is divisible by five you say "Buzz". So now your maths teacher is pointing at all of your classmates in turn, and they happily shout "one!", "two!", "Fizz!", "four!", "Buzz!"... until he very deliberately points at you, fixing you with a steely gaze... time stands still, your mouth dries up, your palms become sweatier and sweatier until you finally manage to croak "Fizz!". Doom is avoided, and the pointing finger moves on. Until the next time."
coding-dojo  agility  learning-by-doing  self-assessment  TDD  BDD  training  kata 
march 2010 by Vaguery
Developer Quality! … and Certification? | xProgramming.com
"I am confident that the Scrum Alliance sees the need for developer improvement, and that they are working toward making their members aware of the need. I am confident that they are working to provide resources that Scrum teams can use to begin to build the skills that they need. And I’m dedicated to influencing them in the right direction, and to bringing as many people into the situation to help accomplish that.

In the end, what I care about is software development, as narrow and geeky as that might be. I care about other people finding the joy in the craft that I’ve found, and that means they have to discover the joy of life-long learning. I think this Scrum Alliance effort can help with that, and I think that “certification” has little or nothing to do with it. What counts will be what we tell the people who show up."
software-development  agility  certification  Scrum  credentialing  pedagogy  worklife 
march 2010 by Vaguery
Did Your Boss Thank You For Coding Yourself to Death?
"Studies about productivity declines when working more than 40 hours a week surface with disturbing regularity. As a developer your creativity declines, you make more mistakes, you miss existing issue etc., to the point where you're doing more harm than good. Should I even mention the health concerns when you spend that much time engaged in the same activity (they even had rules about spending too much time at work in the Soviet Union, and those guys were all about putting in the time for the good of the people). What about diet, you can only survive on coke for so long – poor John couldn't even make it to 40."
sustainability  sustainable-pace  agility  business-culture  software-development-vs-programming 
march 2010 by Vaguery
The Hacker Chick Blog: Are We Agile Yet?
"The following questions can (and should) be applied not only to the new agile practices you select, but also to the existing practices your team is following. Keep in mind that becoming more agile means not only adopting new, agile practices, but also eliminating the old ones that are holding you back from that agile nirvana…"
agility  guidelines  software-development  self-organization  self-assessment 
february 2010 by Vaguery
Against SEMAT « Catenary
"The rest of the items in SEMAT’s proposal are mush. Of course our theories need to address technological and social issues. Of course they need wide support by several communities to be successful. Of course they must be flexible. But what should they consist of? What stake is SEMAT putting on the ground? Unfortunately, beyond a wish to be more like an engineering discipline, this proposal is completely vague, and therefore I cannot support it."
engineering-philosophy  engineering-design  cultural-assumptions  bad-philosophy  agility  project-management  theory-and-practice-sitting-in-a-tree 
february 2010 by Vaguery
..but if the Scrum Alliance Can’t Do It, Who Will? - Cory Foy, LLC - Agile Training and Consulting - Enterprise Agility Redefined
"new Scrum::BaseScrum() //raise NotImplementedException"
Scrum  agility  agile-practices  communities-of-practice  community-dynamics 
february 2010 by Vaguery
japh(r): Retrospective: Week One
"Simply put, you will not improve unless you strive to get better. You will not improve unless you:
look back on what you accomplished
reflect on what prevented you from doing even better
try to apply lessons learned the next time around
It almost seems so obvious that it's not worth the 15 minutes that it takes your team. But, as anyone that has ever practiced regular retrospectives knows, they are an invaluable tool for identifying group problems that might have otherwise gone unnoticed."
retrospectives  agile-management  agility  agile-practices  project-management  self-organization 
february 2010 by Vaguery
The Agile Flywheel « The Agile Executive
"Scrum set the flywheel in motion and caused the rest of the IT process life cycle to respond. ITIL’s processes still form the solid core of service support and we’ve improved the processes’ capability to handle intense work velocity. The organization adapted by developing unprecedented speed in the ability to deliver production fixes and to solve root cause problems with agility."
agility  project-management  business-culture  disintermediation-in-action  innovation  communities-of-practice  management 
february 2010 by Vaguery
[PDF] Application of Large-scale Layout Optimization Techniques in Structural Engineering Practice
"It was also realised that had the layout optimization solver been incorporated within a user-friendly interactive software package, then it would have been very much easier to rapidly change the design problem in response to feedback from other members of the design team..."
engineering-design  optimization  mechanical-engineering  genetic-programming-target  multiobjective-optimization  user-experience  agility  inagility  modeling 
february 2010 by Vaguery
Dan's Blog - Pivotal Tracker API - new version (V3) to be released on Jan. 23
"We're planning a Pivotal Tracker upgrade on Jan 23. As part of this release, we will be introducing a new API version (V3), which will make it easier to follow project activity, allow you to add file attachments, move (re-prioritize) stories, associate source commits with stories, and more."
API  Pivotal-Tracker  project-management  tools  software-development  agility  agile-management 
january 2010 by Vaguery
Keeping computers from ending science's reproducibility
"The idea is that the researchers that rely on computational techniques as part of their day-to-day activities need an entire "reproducible research system" that will make it easier for them to document the sources of their data and the analyses performed on it. The system they've designed shares features with rapid application development environments, as it graphically represents modular computational tools, which can be ordered to create an analysis pipeline, and the individual settings for each can be tweaked. Once complete, the user can trigger the analysis to run; the system documents all of the relevant settings and software information."
agility  open-science  reproducibility  academic-culture  academics-shouldn't-design-interfaces  arguments-against-interns 
january 2010 by Vaguery
Elisabeth Hendrickson's Photos - Hamsters run the WordCount Simulation | Facebook
Elisabeth Hendrickson builds a suite of diorama scenes based on her WordCount Simulation of project management, a great exercise I've had the pleasure to participate in, and which I recommend to anybody working in "knowledge work".
agility  agile-management  simulation 
december 2009 by Vaguery
Economist's View: "How Have Quantitative Financial Models Been Used and Misused?"
"There are important uses for financial products, even complicated ones, so I don't want to impugn innovation generally, but I also don't want to adopt the position that it was all useful - it clearly wasn't and stronger regulatory oversight is needed. As for the defense of financial models and innovation described above, the statement that innovation generally is the source of economic growth, therefore financial innovation must also be good, isn't much help. Similarly, if saying "models benefit many fields, such as airline safety, and not only financial markets" is the best defense of risk models available, that's telling."
modeling  management-failure  learning-from-data  learning-by-watching  map-is-not-the-territory  financial-crisis  finger-pointing  agility  inagility 
december 2009 by Vaguery
Gojko Adzic » Eight interesting techniques to test how a project is going
"Pick up a document, turn it over and see what’s on the back. If you find diagrams, that suggest the need for clarity as people were drawing on it to explain things."
complexity  project-management  social-engineering  agility  agile-management  rules-of-thumb  metrics  XP 
december 2009 by Vaguery
Informative Build | bigvisible.com
"An Informative Build is a build that tells us what the state of our development is so that we can make an informed decision. We need an informative build, because otherwise Continuous Integration is just a waste of our time.

That’s right, I said Continuous Integration is a waste of time. It is a waste of time, because simply running a build doesn’t help us unless that build can also tell us what we need to do. An Informative Build:

Fails when something is wrong, letting us know that our system is broken and we must fix it.
When it fails it tells us precisely why it failed so that we know what we have to do to fix it.
When nothing is wrong it doesn’t fail. We shouldn’t be wasting cycles chasing down errors due to brittle tests or external dependencies."
continuous-integration  extreme-programming  agility  practice  test-driven-development  test-driven-design  productivity  software-development  mythology 
november 2009 by Vaguery
David Harvey - Teams and Technology
"Let’s make the other deliverable explicit: the team, and it’s growing capability.

I’m increasingly interested in the effect that social objects have on the way we work. There’s a growing body of research that demonstrates the ways in which our environment affects our behaviour[1]. The scrum picture has become a social object around which groups form - you see it in books, presentations, printed and stuck on walls, even (here at the Munich Scrum Gathering) on tattoos (the stick-on variety, though I wonder if any of the diehards has gone as far as making it permanent…). I worry about what happens when we surround ourselves with process pictures which (1) don’t include people, and (2) only tell half the story. As soon as we regard ourselves as “means” to some other group’s “ends”, or even worse to some process’s, we are disempowering ourselves (thanks to Ari Tikka in his Scan-Agile 2009 presentation for pointing this out)."
agility  models  software-development  Scrum  worklife  value-fetishism 
october 2009 by Vaguery
Exploration Through Example » Blog Archive » Drive out waste
"Now, as Jonathan Kohl would point out, many people marching behind the Agile banner do the same: they use Agile as another club with which to beat people. I’m less worried about Agile, though, because its base rhetoric is more explicitly humanist. Lean is more likely to be an attractive nuisance because the idea of driving out waste appeals to executives who find it less work to remove waste than to convert it into value—executives who get license to act sociopathic because they have a fiduciary duty to treat business as a machine for maximizing shareholder value, externalities be damned. I worry about Lean in a business culture where we are trained out of empathy for Lear, damned fool though he surely is."
lean  agile  business-culture  agility  Taylorism  management  social-norms  social-engineering  worklife 
october 2009 by Vaguery
Software Engineering - Best Practices: [Misc] Clean Code Developer
"So as my new years recommendation I would be happy if you can check out the website given above and join the idea of a clean code awareness."
craftsmanship  programming  clean-code  agility 
october 2009 by Vaguery
The Agile Skills Project | xProgramming.com
What I'll be doing in November

"The Agile Skills Project is a non-commercial resource that will establish a common baseline of the skills an Agile developer needs to have, including a shared vocabulary and understanding of fundamental practices. The Project intends to:

establish an evolving picture of the skills needed on Agile projects;
encourage life-long continuous learning;
establish a network of trust to help members find like-minded folk, and to identify new mentors in the community."
agility  social-norms  social-engineering  accreditation  credentialing  disintermediation-in-action  collective-attention 
october 2009 by Vaguery
Seth's Blog: If TV ads were free
"By the time we tell you the right answer, it'll be too late."
also:academia  also:newspapers  marketing  business  agility  work  business-culture  pedagogy  expertise  learning-by-doing 
september 2009 by Vaguery
Agility@Scale: Strategies for Scaling Agile Software Development
"Recognize that there is a demand for certification. The agile community needs to put together a decent certification program, something that the Scrum Alliance has clearly failed at doing. My article Coming Soon: Agile Certification provides some thoughts as to what we need to do. The good news is that people such as Ron Jeffries and Chet Hendrickson, and others, are putting together a developer certification program. The really good news is that these are the right people to do this. The really bad news is that they’re doing it under the aegis of the Scrum Alliance, so whatever they accomplish will unfortunately be tainted by the fallout of the CSM debacle."
credentialing  credentials  certification  Scrum  agility  social-norms 
september 2009 by Vaguery
Agile Commentary: Post agile, one third of you will be gone...
This needs to happen to Universities: "…yes, we lost a lot of people. The people that just wanted to tell other people what to do were gone. They either left or were removed. The people who liked sitting in cubes and being told what to do left also."
agility  management  business-culture  academic-culture  scalability  cultural-norms  buh-bye 
july 2009 by Vaguery
http://agileroots2009.confreaks.com/videos/16-jun-2009-09-00-artisanal-retro-futurism-team-scale-anarcho-syndicalism-brian-marick-small.mp4
video  conferences  agility  agile-management  revolution  social-norms  social-networks  propaganda  history-is-a-feature-not-a-bug  kawgooshkawnick  not-an-employee 
july 2009 by Vaguery
One day in Kanban land - Henrik Kniberg's blog
project-management  agility  kanban  Scrum  agile  lean 
july 2009 by Vaguery
scrumalliance's Profile - GitHub
Redmine plugins for making the platform more project-appropriate.
Redmine  project-management  plugin  burndown  agility  tools 
may 2009 by Vaguery
Agile Ajax » Using Cucumber for Acceptance Testing » Pathfinder Development
"My experience so far, as I explore what Cucumber can do, has been largely positive. Where I was starting with Cucumber and only a vague idea of how the user interaction would play out, writing the scenarios at the Cucumber level felt very valuable and gave the development a clear path that I wouldn't have otherwise had. That said, there is extra code being written, and it's clearly possible to get really tangled in getting the step definitions right."
Cucumber  BDD  behavior-driven-design  Ruby  TDD  Machinist  testing  agility  software-development 
march 2009 by Vaguery
We Tried Baseball and It Didn't Work
"The thing that finally condemns the entire "baseball" idea, however is this: even with all these improvements, the game is no fun at all.

We tried baseball, and it didn't work."
agility  late-adoption  software-development  craft  philosophy  parody  process  resistance-to-change 
march 2009 by Vaguery
Why a manifesto? How... Help shape the InfoQ news item - software_craftsmanship | Google Groups
"Also, over time, as more and more younger developers join the ranks through
established apprenticeship programs, they will write less and less of the
crap code. From the start, they will learn techniques to help improve the
code they write. With the day-to-day help and guidance of an experienced
mentor, they will be saved the frustration of a lot of the 'crap code'
mistakes that I, at least, had to make in order to learn the path that I'm
on now to better my own skills. "
craftsmanship  craftsman  agility  software-development  programming  manifesto 
march 2009 by Vaguery
Agile consulting: The Dangers of Agile
"Everybody knows that agile provides some great ideas if you want to add value to software delivery projects. But what I haven’t seen is a fundamental look at the effects of agile on our health, on our sanity, and the safety of our environment..."
agility  fair-and-balanced  amusing 
march 2009 by Vaguery
Continuous Deployment « Timothy Fitz
"So what should Alex do? Continuously deploy. Every commit should be instantly deployed to production. Let’s walk through her story again, assuming she had such an ideal implementation of Continuous Deployment.
Alex commits. Minutes later warnings go off that the cluster is no longer healthy. The failure is easily correlated to Alex’s change and her change is reverted. Alex spends minimal time debugging, finding the now obvious typo with ease. Her changes still caused a failure cascade, but the downtime was minimal. "
continuous-integration  continuous-deployment  testing  agility  FUD  amusing-comments 
february 2009 by Vaguery
Lessons Learned: Continuous deployment and continuous learning
"Assuming you're with me so far, what will that mean in practice? Throwing out a lot of code. That's because as you get better at continuous deployment, you learn more and more about what works and what doesn't. If you're serious about learning, you'll continuously learn to prune the dead weight that doesn't work. That's not entirely without risk, which is a lesson we learned all-too-well at IMVU. Luckily, Chad Austin has recently weighed in with an excellent piece called 10 Pitfalls of Dirty Code."
programming  software-development  continuous-integration  agility  release-schedule  production  testing 
february 2009 by Vaguery
Wide Awake Developers: Fast Iteration versus Elegant Design
"So why is Linux everywhere, and we only hear about 386BSD in historical contexts? There is exactly one answer, and it's what Eric Raymond was really talking about in The Cathedral and the Bazaar. TCatB has been seen mostly as an argument for open-source versus commercial software, but what Raymond saw was that the real competition comes down to an open contribution model versus closed contributions. Linus' promiscuous contribution policy simply let Linux out-evolve 386BSD. More contributors meant more drivers, more bug fixes, more enhancements... more ideas, ultimately. Two people, no matter how talented, cannot outcode thousands of Linux contributors. The best programmers are 10 times more productive than the average, and I would rate Bill and Lynne among the very best. But, as of last April, the Linux Foundation reported that more than 3,600 people had contributed to the kernel alone."
agility  competitiveness  project-management  planning  collaboration 
february 2009 by Vaguery
Mixing Cucumber with Test::Unit/Shoulda — GIANT ROBOTS SMASHING INTO OTHER GIANT ROBOTS
"We’ve been writing a “feature” for every new client request on that project – for each user-created ticket we handle, we create a .feature file (and include the ticket number in the feature title), and write steps for that request. This means that we have acceptance tests for all new client requests on that project. This approach may seem a little strange, but it’s been helpful, and we’re very happy with it so far. We’ll likely take a different approach if we use Cucumber on a project from scratch.

Now you have no excuse if your projects aren’t doing any kind of top-down testing, so get out there and write some acceptance tests!"
test-driven-development  TDD  behavior-driven-design  BDD  cucumber  shoulda  ruby  testing  agility  emergent-design 
february 2009 by Vaguery
The Bloat at the Edge of Duplication Removal (The Orange Model)
"Here’s what duplication removal does, structurally. It allows you to pull out redundant bits of pulp from big sections, yielding smaller sections, but the side effect is that you end up with more fascia. Duplication removal increases the ratio of fascia to pulp. If the amount of pulp you are able to remove exceeds the size of the fascia you introduce, the net amount of code decreases, otherwise it might increase.

In general, I think that a high fascia to pulp ratio is better for maintenance. It gives us is a higher surface area to volume ratio for our code. This can enhance testability and make it easier to compose new software – we already have smaller more understandable pieces."
project-management  design  emergent-design  agility  refactoring  programming  software-development 
february 2009 by Vaguery
Technical Debt « Hot Needle of Inquiry
generalizable for many domains, not just software development: "However, as a program evolves, there’s a good chance that the Design In Code will not include all the good things we now understand. We have a better Design In Head. When the design in our head is enough better than the one in the code, it can pay off to bring the code closer to what we now understand."
refactoring  software-development  agility  XP  extreme-programming  design  emergent-design  rigor  diligence 
february 2009 by Vaguery
Hot Needle of Inquiry » Blog Archive » Context, My Foot!
"Well, my dear little children, I’ve got bad news for you. It is your precious context that is holding you back. It is your C-level Exeuctives and high-level managers who can’t delegate real responsibility and authority to their people. It is your product people who are too busy to explain what really needs to be done. It is your facilities people who can’t make a workspace fit to work in. It is your programmers who won’t learn the techniques necessary to succeed. It is your managers and product owners who keep increasing pressure until any focus on quality is driven out of the project."
agility  management  change  worklife  practice  rigor 
february 2009 by Vaguery
Traps & Pitfalls of Agile Software Development - A Non-Contrarian View
"1. Agile teams may be prone to rapid accumulation of technical debt. The accrual of technical debt can occur in a variety of ways. In a rush to completion, Iterative development is left out. Pieces get built (Incremental development) but rarely reworked. Design gets left out, possibly as a backlash to BDUF. In a rush to get started building software, sometimes preliminary design work is insufficient. Possibly too much hope is placed in refactoring. Refactoring gets left out. Refactoring is another form of rework that often is ignored in the rush to complete. In summary, the team may move too fast for it's own good...."
agility  teams  design  management  programming  development  social-norms  failure 
january 2009 by Vaguery
A List Apart: Articles: Getting Real About Agile Design
/replace "design" with "science"/ as well

"Fortunately, we can learn from other fields. Filmmakers operate in a similarly agile fashion, filming scenes in an order dictated purely by logistics. To ensure vision, coherence, and narrative continuity they employ specialists: directors and script supervisors. On the web, designers can play a similar role, but must volunteer and adapt it for themselves. This means getting involved in writing user stories and trying to guide product owners away from over-hasty solutions."
design  agility  cultural-norms  project-management  development  management  productivity  methodologies 
january 2009 by Vaguery
Making Agile a Reality | Agile 2009
"Agile 2009 will be an exciting international conference about techniques and technologies, attitudes and policies, research and first-hand experience, from both the management and technical sides of agile software development. The agile approach focuses on delivering business value early in the project lifetime and being able to incorporate emergent requirements. It accentuates the use of rich, informal communication channels and frequent delivery of running, tested systems, while attending to the human component of software development.

... The conference is not about a single methodology or approach, but rather provides a forum for the exchange of information regarding all agile development technologies."
agility  agile-management  conferences  conference  software 
december 2008 by Vaguery
Pandemonium [Tesugen]
"XP argues that for emergent design to work, you need to keep the code as simple as possible – no unnecessary complexity – and to refactor as you learn. It is also important, XP says, to program in pairs and to frequently switch who sits with whom, so that everyone on the team has spent time with each part of the system. Then everyone must be present in all meetings and work in an office space that encourages communication."
extreme-programming  XP  agility  emergence  musing  philosophy  institutional-design  risk-management 
december 2008 by Vaguery
The Other Half of "Artists Ship"
"The purpose of the committee is presumably to ensure that the company doesn't waste money. And yet the result is that the company pays 10 times as much."
via:nielsen  software  professionalism  decision-making  management  business-culture  open-source  agility  cultural-norms  disintermediation 
november 2008 by Vaguery
Mock - Mocking and Test Utilities
programming  development  library  tools  Python  testing  TDD  agility 
october 2008 by Vaguery
The Programming Aphorisms of Strunk and White (James Devlin)
via:arsyed  programming  style  writing  clarity  agility  communication 
october 2008 by Vaguery
Charlie's Diary: The bumpy ride hits toytown
"We've never actually seen a true global recession in a Web 2.0 world. What's it going to look like? How is it going to differ from a recession in a pre-internet world? Is it going to accelerate the hollowing-out of the retail high street as economy-conscious shoppers increasingly move to online shopping and comparison systems like Froogle? Are we going to see homeless folks not only living in their cars but telecommuting from them, using pay-as-you-go 3G cellular modems, cheap-ass Netbooks, and rented phone numbers to give the appearance of still having a meatspace office? Is the increasing performance curve of consumer electronics going to give way to a deflationary price war as embattled producers try to hold on to market share as Moore's Law cuts the ground away from beneath their feet?"
futurism  economics  finance  crisis  web2.0  agility  agile-management  social-engineering  business-model  business-culture  supply-chains 
october 2008 by Vaguery
Evolving Web: What Kills Innovation
General point: "How can people of good conscience within such populations change the cultures that are stifling them?"
innovation  cultural-norms  change  social-engineering  business-culture  business-plan  sustainability  agility 
july 2008 by Vaguery
Scrum-ban | Lean Software Engineering
via:dunrie  when-you-don't-have-time-to-talk  Scrum  agility  productivity  process-control  lean 
july 2008 by Vaguery
AgileAgenda - Project Scheduling made simple
agility  GSD  via:dunrie  GTD  scheduling  task  management  planning  software 
july 2008 by Vaguery
commonspace: Agile philanthropy: how our fellowships work
philanthropy  mission  funding  openness  agility  agile-management  public-policy 
june 2008 by Vaguery
Coding Horror: Don't Go Dark
agility  transparency  openness  open-source  collaboration  software  development  community  programming 
june 2008 by Vaguery
Nassim Nicholas Taleb: the prophet of boom and doom
"Go to parties. You can’t even start to know what you may find on the envelope of serendipity"
advice  interview  serendipity  innovation  extreme-values  prediction  agility 
june 2008 by Vaguery
Why You Should Think Seriously About Being Less Efficient | Slow Leadership
"Effectiveness uses time to avoid doing only what you have done before, in favor of working out how to do something better."
agility  advice  GTD  productivity  success  worklife 
may 2008 by Vaguery
dave astels » Why Your Code Sucks
Just worth posting on the wall, is all.
rules  agility  programming  software  development  coding  design  testing  TDD  BDD 
april 2008 by Vaguery
Modus Cooperandi
agile-management  consulting  agility  management  business-culture  worklife 
march 2008 by Vaguery
Nudge > A little Push
One of the reasons I've been kind of quiet lately.
Nudge  genetic-programming  symbolic-regression  machine-learning  open-source  tools  visualization  Python  programming  development  agility  agile  scientific-computing  statistics 
march 2008 by Vaguery
O'Reilly Network -- Behavior Driven Development Using Ruby (Part 3)
BDD  behavior-driven  Rails  Ruby  programming  development  agility  design 
march 2008 by Vaguery
Six Principles for Making New Things [Paul Graham]
via:vielmetti  via:plindberg  design  agility  essay  reflection  innovation  business-culture  philosophy  problem-solving  tools 
february 2008 by Vaguery
peripatetic axiom: Complexity and Test-first 0
testing  software  development  TDD  agility  metrics  quality 
february 2008 by Vaguery
Confessions of a Community College Dean: Ask the Administrator: Slowly...Slowly...
"Shared governance takes time."
academia  cultural-norms  decision-making  management  style  pace  agility  inagility  collaboration  freedom  direction 
january 2008 by Vaguery
Nested Example Groups
Love the example
rspec  Ruby  RoR  Rails  BDD  behavior-driven-development  specification  agility  agile-management  requirements  programming 
december 2007 by Vaguery
The Cross-Discipline Design Imperative
And also: will bitch-slap next person to use phrase "an evolution" as a noun, in any context. Period.
agility  design  designers  generalist  innovation  business-culture  trends  generalism 
november 2007 by Vaguery
Knowing and Doing: October 2007 Archives
agility  agile-management  problem-solving  design  pedagogy  project-management  structure 
october 2007 by Vaguery
State of Flow: Estimation XPeriment::journal
agility  agile-management  planning  project-management  extreme-programming  XP  decision-making  business-plan  decision-support 
september 2007 by Vaguery
J. LeRoy's Evolving Web: Atomic Agility 2
A bit rough, but, "Information that stops at a given individual helps no one. The Agile Manager should design social media systems to churn any information received during a project."
agility  agile-management  management  teams  advice  business-culture 
september 2007 by Vaguery
Richard's Braindump: Fixed Price Contracts and Agile Delivery
"The firm figured that they'd do what they could within the strict terms of the initial contract and then pick up extra time through massive overestimation on change requests."
agility  planning  accounting  business-plan  contracting  fixed-price  contracts  control 
september 2007 by Vaguery
J. LeRoy's Evolving Web: I NEED TO BE FIXED!
"Agile teams are at the forefront of a movement. But the front lines are the bloody lines. We're going to get knocked around a little."
agility  business-culture  business-plan  extreme-programming  marketing  planning  accounting  evangelism  commitment 
september 2007 by Vaguery
The Founding of the Agile Alliance
agility  history  agile  software  development 
august 2007 by Vaguery
What is Lean - Principles
lean  management  methodologies  agility  productivity 
july 2007 by Vaguery
« earlier      

related tags

academia ⊕  academic-culture ⊕  academics-shouldn't-design-interfaces ⊕  accounting ⊕  accreditation ⊕  adaptation ⊕  advice ⊕  agile ⊕  agile-management ⊕  agile-practices ⊕  agilism ⊕  agility ⊖  algorithms ⊕  also:academia ⊕  also:newspapers ⊕  amusing ⊕  amusing-comments ⊕  anecdote ⊕  API ⊕  architecture ⊕  arguments-against-interns ⊕  assumptions ⊕  authors ⊕  bad-philosophy ⊕  bdd ⊕  beginner's-mind ⊕  behavior-driven ⊕  behavior-driven-design ⊕  behavior-driven-development ⊕  benchmarking ⊕  best-practices ⊕  blogging ⊕  book ⊕  books ⊕  budgeting ⊕  buh-bye ⊕  burndown ⊕  business ⊕  business-culture ⊕  business-model ⊕  business-plan ⊕  business-value ⊕  certification ⊕  change ⊕  Chet-Hendrickson ⊕  clarity ⊕  clean-code ⊕  cluelessness ⊕  coauthorship ⊕  coding ⊕  coding-dojo ⊕  coevolution ⊕  cognition ⊕  collaboration ⊕  collective-attention ⊕  comments ⊕  commitment ⊕  communication ⊕  communities-of-practice ⊕  community ⊕  community-dynamics ⊕  competitiveness ⊕  complexity ⊕  conference ⊕  conferences ⊕  conservation ⊕  consulting ⊕  continuous-deployment ⊕  continuous-integration ⊕  contracting ⊕  contracts ⊕  control ⊕  craft ⊕  craftsman ⊕  craftsmanship ⊕  creativity ⊕  credentialing ⊕  credentials ⊕  crisis ⊕  cucumber ⊕  cultural-assumptions ⊕  cultural-norms ⊕  data ⊕  decision-making ⊕  decision-support ⊕  design ⊕  designers ⊕  development ⊕  diligence ⊕  direction ⊕  disintermediation ⊕  disintermediation-in-action ⊕  documentation ⊕  ecology ⊕  economics ⊕  ecosystems ⊕  editing ⊕  education ⊕  emergence ⊕  emergent-design ⊕  engineering ⊕  engineering-design ⊕  engineering-philosophy ⊕  entrepreneurship ⊕  essay ⊕  estimates ⊕  evangelism ⊕  experimentation ⊕  experiments ⊕  expertise ⊕  explanation ⊕  exploration-exploitation ⊕  extreme-programming ⊕  extreme-values ⊕  facts ⊕  failure ⊕  fair-and-balanced ⊕  figure-ground-error ⊕  finance ⊕  financial-crisis ⊕  finger-pointing ⊕  fixed-price ⊕  flow ⊕  forecasting ⊕  freedom ⊕  FUD ⊕  funding ⊕  futurism ⊕  generalism ⊕  generalist ⊕  genetic-programming ⊕  genetic-programming-target ⊕  goals ⊕  Google ⊕  GSD ⊕  GTD ⊕  guidelines ⊕  happiness ⊕  heuristics ⊕  hints ⊕  history ⊕  history-is-a-feature-not-a-bug ⊕  humor ⊕  immersion ⊕  inagility ⊕  information-architecture ⊕  innovation ⊕  insight ⊕  institutional-design ⊕  interview ⊕  journals ⊕  kanban ⊕  kata ⊕  kawgooshkawnick ⊕  knowledge ⊕  Lakatos ⊕  late-adoption ⊕  lean ⊕  learning ⊕  learning-by-doing ⊕  learning-by-watching ⊕  learning-from-data ⊕  library ⊕  machine-learning ⊕  Machinist ⊕  management ⊕  management-consulting ⊕  management-failure ⊕  manifesto ⊕  map-is-not-the-territory ⊕  Mark-Poppendieck ⊕  marketing ⊕  mechanical-engineering ⊕  methodologies ⊕  metrics ⊕  milestones ⊕  military ⊕  mission ⊕  modeling ⊕  models ⊕  motivation ⊕  multiobjective-optimization ⊕  musing ⊕  mythology ⊕  network-culture ⊕  not-an-employee ⊕  Nudge ⊕  objectives ⊕  on-second-thought ⊕  open-access ⊕  open-science ⊕  open-source ⊕  openness ⊕  optimization ⊕  pace ⊕  pair-programming ⊕  parody ⊕  pedagogy ⊕  philanthropy ⊕  philosophy ⊕  philosophy-of-engineering ⊕  philosophy-of-science ⊕  Pivotal-Tracker ⊕  planning ⊕  plugin ⊕  podcast ⊕  practice ⊕  prediction ⊕  problem-solving ⊕  process ⊕  process-control ⊕  prod ⊕  production ⊕  productivity ⊕  professionalism ⊕  programming ⊕  progress ⊕  project-management ⊕  propaganda ⊕  psychology ⊕  public-policy ⊕  publishing ⊕  Python ⊕  quality ⊕  Rails ⊕  Redmine ⊕  refactoring ⊕  reflection ⊕  release-schedule ⊕  reproducibility ⊕  requirements ⊕  rescinded ⊕  research ⊕  resistance-to-change ⊕  retrospectives ⊕  revolution ⊕  rigor ⊕  risk-management ⊕  Ron-Jeffries ⊕  RoR ⊕  rspec ⊕  ruby ⊕  rules ⊕  rules-of-thumb ⊕  scalability ⊕  scheduling ⊕  science ⊕  scientific-computing ⊕  Scrum ⊕  self-assessment ⊕  self-help ⊕  self-organization ⊕  serendipity ⊕  shoulda ⊕  simulation ⊕  social-engineering ⊕  social-networks ⊕  social-norms ⊕  software ⊕  software-development ⊕  software-development-is-not-programming ⊕  software-development-vs-programming ⊕  software-engineering ⊕  specification ⊕  speech ⊕  startup-culture-must-die ⊕  startups ⊕  statistics ⊕  stereotypes ⊕  story ⊕  strategy ⊕  structure ⊕  style ⊕  subjective-optimization ⊕  success ⊕  supply-chains ⊕  sustainability ⊕  sustainable-pace ⊕  symbolic-regression ⊕  task ⊕  Taylorism ⊕  TDD ⊕  teams ⊕  technical ⊕  test-driven-design ⊕  test-driven-development ⊕  testing ⊕  theory-and-practice-sitting-in-a-tree ⊕  tools ⊕  toyota ⊕  training ⊕  transparency ⊕  trends ⊕  user-experience ⊕  value-fetishism ⊕  venture-capital ⊕  via:arsyed ⊕  via:bkerr ⊕  via:dunrie ⊕  via:nielsen ⊕  via:objectmentor ⊕  via:plindberg ⊕  via:vielmetti ⊕  video ⊕  visualization ⊕  web-design ⊕  web2.0 ⊕  what-gets-measured-gets-fudged ⊕  what-you-call-things-really-matters ⊕  when-you-don't-have-time-to-talk ⊕  work ⊕  worklife ⊕  workshop ⊕  writing ⊕  XP ⊕ 

Copy this bookmark:



description:


tags: