A startup is an organization formed to search for a repeatable and scalable business model.
— Steve Blank
A ‘startup’ is a company that is confused about:
- What its product is.
- Who its customers are.
- How to make money.
As soon as it figures out all 3 things, it ceases being a startup and becomes a real business.
— Dave McClure
Regardless of the definition of a Startup that you may choose or you adhere to, one thing is common… Speed.
Have you ever been on a team? Have you tried to collaborate efficiently?
If so, you probably searched for tools that could make it work better for everyone. This post (which will be completed in two parts) is meant to share our experience on the subject and describe both the tools we end up using and the process we follow.
One of a team’s initial tasks is the selection of an appropriate work process, a way for its members to collaborate efficiently.
You can typically get there either by using a whiteboard and some post-it’s or by picking a tool that can solve the problem for you.
I tend to rely on the latter.
Working more and more with Kanban and Scrum methodologies made me create a presentation deck for a basic Kanban Introduction. Here it is , I hope you like it.
If you are in Greece you are welcome to join our meetup http://www.meetup.com/Agile-Greece/
If you are not you are welcome to follow us in twitter: https://twitter.com/AgileGRmeetup
If you want a more “textier” version of my presentation check this and this and this too…
I love technology and working with people. That is why I am trying to offer as much as I can at the local startup ecosystem and at the same time building Apirise. A platform to reduce time and effort required to integrate and maintain APIs. Simply, fast and efficiently!
I am co-organizer of the Agile Greece and API Athens meetups and I contribute at the Developer Economics Blog.
Discuss with me…
I’d love to know your ideas and thoughts on this post.
Connect with me on Twitter or Google+
You hear about Kanban all the time. There are great guides out there but you do not know where to start. Is this the case? I had the same problem too. So I tried to gather some really baby steps of implementing a simple Kanban system for your early development phase.
You are a startup. A wannabe startup. And you have an idea for a product that will conquer the world. Am I close?
You found the perfect team and you want to build the base for your future company and your product. In a startup you do not know how your product will be in 6 months (maybe less). The product changes, the features change. OK… stop… I will not go down that path, many things change…
Let’s assume for a moment that you came down to 1-2 main features and you want to build your MVP. Would you employ an agile strategy that early?
Having some free time this summer I did a SCRUM reading. I am in the midst of my Scrum Master Certification and I found out about KANBAN!!
It seems a lot of people are reading / practicing Kanban recently. I will try to describe (briefly) how I understand it.