agile

Agile Writing & Development Tools

Writing Tools

1. Markdown Writing Tools for Mac / iPad / iPhone 

  • FoldingText
    • It's Markdown with outline features, Pomodoro like support for timers and more.
    • It beats everything I've tried before especially for long articles. Worth the investment of $25.
    • Demo version on their site. It is Mac only for now.
  • ByWord
    • My favorite iPad / Mac / iPhone editing tool period.

Our Books Recommendations List on Agile, Kanban, Lean and Business Productivity Themes

Summary:

That list gathers the best books to get knowledge on the most important Agile, Kanban, Lean and Business Productivity related themes.

Books on Agile theme:

  • All About Agile: Agile Management Made Easy! by Kelly Waters
  • Agile Estimating and Planning by Mike Cohn
  • Project Retrospectives: A Handbook for Team Reviews by Norman L. Kerth
  • Agile Retrospectives: Making Good Teams Great by Esther Derby, Diana Larsen, Ken Schwaber

What is the Difference between Agile, Kanban and Scrum in less than 5 minutes?

First let us remember that the Agile Movement was born in 2001 in the field of Software Development, at a time when complex and highly ineffective methods and management philosophies were being used to try to deliver software projects. They were collectively called heavy processes, because of the large number of steps they required to get anything done, the Rational Unified Process or RUP is one of them.

The Waterfall Trap

The first 90 percent of the code accounts for the first 90 percent of the development time. The remaining 10 percent of the code accounts for the other 90 percent of the development time.

By Tom Cargill. Bell Labs.

It sounds a bit funny, yet so many times it’s true. The question is why?

The reason is what I call: “The Waterfall Trap.” Any project, at the moment it starts, uses logic, knowledge, experience and good practices to guess the future. That’s right the plan is at best a very good educated guess.

Agile Kanban: Fly Different

Kanban: Fly Different - An Introduction.

Several people have asked me to explain the basics of Kanban’s Agile approach to Software Development. This presentation is a simple, straight forward, fun way to get what Kanban is all about. Feel free to comment on it, or contribute for a future revision.

HKanban - A Holistic Approach to Getting Things Done

Standing on the shoulders of great men.

Like so many Project Managers and busy professionals I too have discovered that is not just enough to manage other people, or the work at hand, we have to manage our efforts in and out of the office, and daily life can be the biggest challenge of all.

The first author to show us ways to improve our productivity was David Allen, his Getting Things Done book was a landmark that I continue to browse occasionally. However I could not get the system to work for me. I wanted something simpler, but still effective.

Beyond the 3 Project Management Constraints - The Agile Kanban Contribution

Traditionally Project Management has identified three constraints that must be managed to achieve success on any project, namely:

  • Time: or the schedule, to meet deadlines and deliver
  • Money: our available budget, and financial resources
  • Scope: extent of work that has to be performed.

Collectively they are known as the Project Management Triangle, and for decades they have been the focal point for the project manager’s efforts.

Kanban Is a Smart Agile Methodology

Out of all the Agile Project Management methodologies out there: Kanban is smart because it makes people think, it listens to them, and it leads to Continuous Improvement. It is not just a recipe.

Yours truly, inspired by the post of Al Shalloway.

It Is Wise to Look Ahead

It is always wise to look ahead, but difficult to look further than you can see.

By Winston Churchill. In Project Management this is a rule, and the consequence to this rule is that the further into the future we try to plan, the less reliable plans become.

However we still must plan! How can we solve this paradox? The answer lies in Agile Methodologies, particularly Lean Kanban. I will explore this subject in the near future.

PMBOK. Visualizing Complexity

Visualizing Complexity. The Project Management Insitute has excelled in examining every single area of the life of a project. And althogh the emphasis has traditionally been Waterfall like projects, their description aids anyone in mapping out the steps of any project, including Agile or Kanban projects. Once we visualize complexity, it's easier to guide our actions.
 

Pages

Subscribe to RSS - agile