Remove Distribution Remove Hiring Remove SCRUM
article thumbnail

The most valuable lessons I learned from managing a virtual team

The Next Web

The difference between “remote” and “distributed” is that in a remote team, there is a company office(s) where some team members are based full-time. A distributed team has no location base – everyone is in a different place. But distributiveness solves a lot of problems, including that of being remote. Hire those you trust.

article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

I would add -- think of your development and running your business like a PM/Developer uses Agile or Scrum in software development. How to get distribution advantage on the iPhone How to Usability Test your Site for Free The one line split-test, or how to A/B all the tim. No more, no less. September 15, 2008 9:19 PM James said.

Lean 168
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Sprint Like An Egyptian: A Tech Entrepreneurship Revolution in Alexandria

Gust

For example, in an area known for a high crime rate, security guards can be hired and other measures taken. Distributed teams can work across multiple countries in ways that make the most efficient use of human capital. Silicon Arabia has engineers in Russia as well as Egypt.)

article thumbnail

Skills Development in Africa: How Wide is the Skills Gap?

Transformify

Post Brexit, many companies in the UK consider distributed teams overseas as an alternative to the shrinking talent pool and high recruitment costs in Britain. 20 % of the project managers are familiar with Scrum, but there are very few product managers – less than 1% of all. Scrum, Agile, Product Management.

Africa 75
article thumbnail

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

There are several ways to make progress evident - the Scrum team model is my current favorite. If you have a true cross-functional team, empowered (a la Scrum) to do whatever it takes to succeed its likely they will converge on the result quickly. When its receding, we rescope. Do you have a spec?

article thumbnail

You don't need as many tools as you think

Startup Lessons Learned

Heres something I can relate to: We used assembla for subversion, scrums, milestones, wikis, and for general organizational purposes. Scrum reports would come in once a month, nobody was actually responsible for anything. We had all the tools in place but we didn’t actually practice agile development.

article thumbnail

An ongoing discussion on linkedin about Offshore Web Development and building a team in Europe.

Scalable Startup

Hire them 8 hours at a time and review daily by skype, g hangout. Our strategy was to move to a distributed model where the entire scrum team works together offshore. Its like hiring a resource once you hire a great resource you never need to worry about it. Work directly with engineers, no company involved.