This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Agile marketing may not be a phrase you hear often, but it’s becoming increasingly popular and important. Traditionally associated with development and product management, agile is a lightweight and, well, agile framework for software development and bringing features and products to market.
Here’s a problem I bet every non-technical founder has experienced: the communication gap between what the biz devteam wants and what the tech team thinks they want, and vice versa. You need to build trust between these teams. Practice AgileDevelopment. Their answers are below. Cross Train Members.
Take the example of a design team prepping mock-ups for their developmentteam. Give the devteam your very first sketches and let them get started. And over time, the developmentteam may be able to start anticipating your needs. That frees up even more development resources, and so on.
Lessons Learned by Eric Ries Sunday, April 26, 2009 Productdevelopment leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in productdevelopment. Its a key lean startup concept.
But I have a special sympathy for the "product manager" in a startup that is bringing a new product to a new market, and doing their work in large batches. I met one recently that is working on a really innovative product, and the stories I heard from their developmentteam made me want to cringe. Nice write-up.
All of us know in software companies that scrum is the most significant agile methodology for handling software projects. In spite of its well-known advantages (flexibility, quick feedbacks, adaptability and better communication), we might be uncertain whether to use this framework or follow a traditional way for the development.
From marketing to productdevelopment, to new software tools and communications, the list is almost endless as to the digital transformations taking place. The AppToolKit by GoLocalApps lets app developers track and share their app reviews, create smart websites, and is fully integrated with the cloud.
One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. The result was a new process of four-week iterative cycles all about throttling new code.
This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agiledevelopment. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Expo SF (May.
To get to this Transition stage, the company needed passionate visionaries who can articulate a compelling vision, agile enough to learn and discover in real time, resilient enough to deal with countless failures, and responsive enough to capitalize on what they learned in order to secure early customers. What’s Next.
Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. What is customer development? Using AdWords to assess demand for your new online. Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa.
Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. At the end of the day, the productdevelopmentteam of a startup (large or small) is a service organization. Does this sound familiar?
You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. So the productdevelopmentteam was busy creating lots of split-tests for lots of hypotheses. Each day, the analytics team would share a report with them that had the details of how each test was doing.
Review and optimization: even after all the project milestones are reached, it’s necessary to take some time to test and review. Let’s discuss some of the necessary project management methodologies for managing a remote team. It keeps the work in progress limited so that the team can focus more on the task at hand.
Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of ProductDevelopment Flow If youve ever wondered why agile or lean development techniques work, The Principles of ProductDevelopment Flow: Second Generation Lean ProductDevelopment by Donald G. Reinertsen is the book for you.
During a lull in her practice she got a serendipitous opportunity to shift gears completely and ended up leading software productdevelopmentteams. Indeed, most of the innovations we've made at Smart Bear in the art of code review have already been duplicated by both commercial and open-source competitors.
Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their productdevelopment process. Even worse, agile wasnt really helping me ship higher quality software.
The technical interview is at the heart of these challenges when building a productdevelopmentteam, and so I thought it deserved an entire post on its own. The six key attributes spell ABCDEF: Agility. To probe for agility, you have to ask the candidate questions involving something that they know little about.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content