Organización
Get flash to fully experience Pearltrees
Leonardo Fibonacci died over 760 years ago but he had a profound effect on mathematics in western civilization. He brought what he had learned from mathematician in north Africa back to Europe and authored the book Liber Abaci , which described such things as the Hindu-Arabic numeral system and place value of numbers. In the book he also showed how a number of mathematical problems were solved using the techniques he had learned, one of which was the growth of a population of rabbits. Although he didn't invent it, that sequence bears his name today, and is seen in many places in nature. The use of the Fibonacci sequence in a slightly modified form has also been popularized in the Agile community as values which can be used to estimate the effort required to deliver work.
Fibonacci Must Die!
See, Pivotal Labs quietly helps dozens of the fastest-growing tech companies in the world, including freight trains like Groupon and Twitter. If your start-up needs to get good coding done quickly, as in lightning fast — or if new hires need to get good at coding quickly — top venture capitalists are likely to look over their shoulder and confide: “Call Pivotal Labs.” I first met the Founder of Pivotal Labs, Rob Mee, when one of the start-ups I advise, TaskRabbit , began working with them. One thing is immediately clear: Rob is obsessed with how to get obscenely high output.
What’s Your Start-up’s “Bus Count”? 7 Myths of Entrepreneurship and Programming
How to Create a Business Model Canvas in Google Docs | Agile Zone
We Recommend These Resources A Business Model Canvas is an easy to use, lightweight and powerful tool for anyone looking to sketch out business models. It is quickly becoming the preferred strategic management tool for start-up organizations. While it is available in .pdf form from Alex Osterwalder’s site , I couldn’t help but feel that companies could benefit from an online, collaborative version of his template.
ISO 20000
KANBAN
Lack of Progress Bar (Lopb) is an Eclipse plugin that tracks how long developers wait for background jobs to complete. By benchmarking the performance of background jobs, Lopb provides developers with metrics on how much of their day was wasted due to overhead introduced by the development tools and infrastructure that they depend on or access through their IDE. Background Jobs in Eclipse (and other Eclipse-based IDEs like IBM RAD, MyEclipseIDE, etc.) …
Lack of Progress Bar
Documenting Requirements For Software Development Projects | Agile Zone
Mitch Pronschinske After 2 hugely successful DZone VIP meetups in Cary, NC (USA) and Colombo, Sri Lanka, a third meetup concluded last month in Sofia, Bulgaria - organized by one of DZone's team members, Jordan Jambazov. See pics and user reflections on the meetup
Bottom-Up Project Estimating | Agile Zone
Mitch Pronschinske After 2 hugely successful DZone VIP meetups in Cary, NC (USA) and Colombo, Sri Lanka, a third meetup concluded last month in Sofia, Bulgaria - organized by one of DZone's team members, Jordan Jambazov. See pics and user reflections on the meetup
This is a question that comes up a lot and for good reason. As a programmer, how the hell am I supposed to learn how to develop web applications? There’s no easy answer and even learning institutions don’t seem to know exactly how to do it; the university I went to doesn’t offer any classes on the topic. So, as most other web developers in the field, I’ve learned by doing and trying. No one told me how to do it, I just started developing something for myself and learned how to develop a web application as a side effect.
How to develop web applications
Planning for Failure - The Problem with Working Overtime
There’s an old programmer quote that goes something like this, When workers work overtime they get fatigued, this should be obvious. It should also be obvious that when people are spending more time working, they’re spending less time resting and getting things done in their personal lives. This means they will be less focused and productive on the job.
• What is a good software architecture in a nutshell? | test.ical.ly
Yesterday Nils posted a new article on PHP hates me about starting quick and dirty rather than with a full blown architecture (German, here’s what Google translate does from it ). This produced the question: What is a good architecture and why are there apparently two opposing trenches supporting quality on the one side and speed of development on the other side? After having had enough time to think about this whilst flying to Spain I came to the conclusion that Nils question whether it would be better to start quick and dirty to fail cheap in case the project is a looser or to stick to a clean and solid architecture and spend more time and money. Does quick always have to be dirty, clean always have to be slow, is dirty always quicker? There has been a comment that assumes that Facebook would not be online today if they concentrated on the architecture right away.
Shove It, FizzBuzz! The First Trait of Successful Developers: Intelligence
A few months ago, I wrote an article titled The Five Traits of Succesful Developers , where I said that, to succeed as a developer, you should possess the following five traits: I go into detail in my book about each one, and I’ve decided to share those details here on the blog, with one post for each of the five traits, so let's take a look at #1. “Knowing a great deal is not the same as being smart; intelligence is not information alone but also judgment, the manner in which information is collected and used.” Developers have to be intelligent, but it’s very difficult to actually teach intelligence. It’s like some people are just born with bigger brains. Employers aren’t generally looking for Albert Einstein smarts, but they are looking for someone who will be able to learn and retain information fairly quickly, as well use reasoning skills whenever necessary.
Decomposition of Projects: How to Design Small Incremental Steps by Tom Gilb
The basic premise of iterative, incremental and evolutionary project management (Larman 2003) is that a project is divided into early, frequent and short duration delivery steps. One basic premise of these methods is that each step will attempt to deliver some real value to stakeholders. While it is not difficult to envisage the steps of construction for a system; there is often difficulty in carrying out decomposition into steps when each step has to deliver something of value to stakeholders , in particular to end-users.3 Simple But Critical Steps For Project Management | Agile Zone
Mitch Pronschinske After 2 hugely successful DZone VIP meetups in Cary, NC (USA) and Colombo, Sri Lanka, a third meetup concluded last month in Sofia, Bulgaria - organized by one of DZone's team members, Jordan Jambazov. See pics and user reflections on the meetupGTD
Mitch Pronschinske After 2 hugely successful DZone VIP meetups in Cary, NC (USA) and Colombo, Sri Lanka, a third meetup concluded last month in Sofia, Bulgaria - organized by one of DZone's team members, Jordan Jambazov. See pics and user reflections on the meetup
3 Simple But Critical Steps For Project Management | Agile Zone
From the Mule’s Mouth » Blog Archive » Implementing Kanban for Sustaining Engineering
I’ve been working at MuleSoft on the Sustaining Engineering team for a few months. In this time I watched how things work and find out what type of challenges we deal everyday have and how we solved them. I watched a great team working long hours to solve customers problems as fast as possible. Our primary goal is to enable our customers to meet their deadlines, and remove any problem they might have with MuleSoft’s products in the process.Waste #6: Task Switching
We Recommend These Resources Welcome to episode six of our series "The Seven Wastes of Software Development." In episode one , we introduced the concept of eliminating waste from our software development efforts. Waste elimination can be traced all the way back to the the mid-1900's, the birth of lean manufacturing, and the Toyota Production System (TPS). This is how Taiichi Ohno, the father of the TPS, described its essence: All we are doing is looking at the time line, from the moment the customer gives us an order to the point when we collect the cash.Job seeking tecnics