Remove Agile Remove Lean Remove Security
article thumbnail

Startups – Integrating Security Mindset and Processes Early

YoungUpstarts

The Lean Startup.”. Agile Methodology.”. In the chase to produce the best minimum viable product or to push out the next killer feature, security is often given the backseat. Security is often not given the consideration it should get early in the design or development process and it tends to be costlier to implement later on.

Security 206
article thumbnail

The Future of Government: Hayward & the Lean Startup

Startup Lessons Learned

Guest post by Jennifer Maerz, contributing editor of Lean Startup Co. It’s been exciting to watch the Lean Startup movement grow from a practice utilized in the tech world to one implemented in a wide variety of sectors ranging from enterprise to education, religious organizations, nonprofits, and government groups.

Insiders

Sign Up for our Newsletter

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

Trending Sources

article thumbnail

Hacking for Defense @ Stanford 2021 Lessons Learned Presentations

Steve Blank

Hacking for Defense has teams of students working to understand and solve national security problems. While all the teams used the Mission Model Canvas , (videos here ), Customer Development and Agile Engineering to build Minimal Viable Products, each of their journeys was unique. Our goal was to teach both theory and practice.

Lean 417
article thumbnail

Minimum Viable Product: a guide

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. Thanks Eric. Expo SF (May.

article thumbnail

Hacking for Defense @ Stanford 2020 Lesson Learned Presentations

Steve Blank

The eight teams spoke to over 945 beneficiaries, stakeholders, requirements writers, program managers, warfighters, legal, security, customers, etc. All the teams used the Mission Model Canvas , (videos here ) Customer Development and Agile Engineering to build Minimal Viable Products, but all of their journeys were unique.

Oakland 315
article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. Most of this was code that not scalable, not secure, and not particularly extensible. Great related post by John Shook at the Lean Enterprise Institute about technical vs. social sides of problems. The Lean Startup Intensive is tomorrow at Web 2.0.

article thumbnail

Why Continuous Deployment?

Startup Lessons Learned

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.