![]() ![]() Close, daily cooperation between business people and developers 5. Working software is delivered frequently (weeks rather than months) 4. Welcome changing requirements, even in late development 3. Customer satisfaction by early and continuous delivery of valuable software 2. If you're not familiar with Agile Software Development, you should be (take a few minutes to scan the wikipedia article).Įvery software team I've worked with has their own flavor of how exactly to roll with Agile, but the principles are essentially the same: 1. How, then, do we communicate and plan effectively? Agility ![]() Or I'm happy to never recall the moment I realized there's a bug in the plugin we decided to use, after spending 5 hours thinking it was my fault for not reading the documentation right.īUT, especially as I roll further into my second decade doing this work, occasionally the stars align, things go smoothly, and my team is ready many weeks in advance. I somehow forget that time I wasted ten hours scouring API documentation and Google searches because I spelled “prototype” incorrectly as “pototype” - and of course the error message pointed me in a misleading direction (arg!). As an engineer and product manager in startup land, I always think building a product will take less time than it actually does. If you've been in or around any part of this story, you know it well. Why didn't the engineer just say “about 20 weeks” and aim for delivering a tad early? After an additional seven weeks of ironing out the basic bugs and UX kinks, marketing finally feels comfortable promoting it. Eleven weeks later, it's delivered (and it's not very good). The marketer rolls her eyes, of course, and expects it in five. “Sure, we'll have that done in three weeks.” says the engineer. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |