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
Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.
While I am currently a passionate advocate of methodologies like Agile, Lean, Design Thinking, Customer Development and more, I try very hard not to get too attached to, or to be too closely associated with, any particular school of thought or technique. Then of the people and teams I work with. Or Six Sigma. I could go on.
But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuousdeployment, youd better be able to certify that build too, which brings us to. For more on continuousdeployment, see Just-in-time Scalability. Can you make a build in one step?
XP and Scrum don’t have much to say - they punt. If you look at the origins of most agile systems, including Scrum and XP , they come out of experiences in big companies. Both Scrum and XP had a role which you could happily call by the modern title "Product Manager". Embedded in that assumption is why startups fail.
These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.
I would add -- think of your development and running your business like a PM/Developer uses Agile or Scrum in software development. Case Study: Continuousdeployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuousdeployment for mission-critical applica.
And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development. When people ask about how to reconcile metrics with interaction design, usability testing, or in-person customer interviews, this is the issue they are really talking about. Excellent post.
To begin with, see if you can get designers, programmers, and QA on the same team together. The advantages of cross-functional teams are well documented, and for a thorough treatment I recommend the theory in the second half of Agile Software Development with Scrum. Case Study: Continuousdeployment makes releases n.
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. And wait until you see a "non-technical" designer writing simple code to try and speed up a release.
At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. Case Study: Continuousdeployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuousdeployment for mission-critical applica.
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