Podcasts about software estimation

In this episode, the penultimate episode in the Software Estimation mini-series, I want to discuss how Software Estimation works in terms of professionalism - and in many cases, surprisingly, the professional response is not to provide an estimate. ----- Find this episodes show notes at: https://red-folder.com/podcasts/204 Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

This episode is part of a wider mini-series looking at Estimation in Software Development. In this episode, I wanted to look at the impact that dependencies have on software estimation. This episode was inspired by a blog post on scrum.org entitled "Eliminate Dependencies, Don't Manage Them", which I read while preparing this series. In brief, the article talks about how you're better off eliminating dependencies rather than trying to manage them through normal traditional management processes. In his book, Software Estimation, Demystifying the Black Art, Steve McConnell says that size of the software is the single most significant contributor to project effort and schedule. Personally, I'd like to suggest that dependencies, if not of similar importance, are a close second. ----- Find this episodes show notes at: https://red-folder.com/podcasts/197 Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Welcome back to Season 2 of ByteSized RSE, a program supported by Universe-HPC http://www.universe-hpc.ac.uk .The subject for this session is: Software Estimation and some ideas on how to approach it. Things mentioned in this episode:The Mythical Man Month, Frederick Brooks, 1975, Software Estimation, Steve McConnell, https://www.google.co.uk/books/edition/Software_Estimation/U5VCAwAAQBAJ?hl=en&gbpv=0https://rclayton.silvrback.com/software-estimation-is-a-losing-game a critical view on software estimation by Richard Claytonhttps://www.stepsize.com/blog/the-best-software-estimation-techniques an overview of some estimation techniqueshttps://en.wikipedia.org/wiki/Planning_poker The Planning Pokerhttps://en.wikipedia.org/wiki/Three-point_estimation 3-point estimationByte-sized RSE is presented in collaboration with the UNIVERSE-HPC project.https://www.imperial.ac.uk/computational-methods/rse/events/byte-sized-rse/ByteSized RSE link to Imperial CollegeAudio clips:Frying sound: https://www.fesliyanstudios.com/royalty-free-sound-effects-download/frying-cooking-food-34"Golden Girls" S6E15:  one of the many YouTube videos with Bea Arthur's (aka Dorothy Zbornak) best lines. Support the Show.Thank you for listening and your ongoing support. It means the world to us! Support the show on Patreon https://www.patreon.com/codeforthought Get in touch: Email mailto:code4thought@proton.me UK RSE Slack (ukrse.slack.com): @code4thought or @piddie US RSE Slack (usrse.slack.com): @Peter Schmidt Mastadon: https://fosstodon.org/@code4thought or @code4thought@fosstodon.org LinkedIn: https://www.linkedin.com/in/pweschmidt/ (personal Profile)LinkedIn: https://www.linkedin.com/company/codeforthought/ (Code for Thought Profile) This podcast is licensed under the Creative Commons Licence: https://creativecommons.org/licenses/by-sa/4.0/

Episode Notes Veradept: https://veradept.com/ elm-conf: https://2020.elm-conf.com/about ‘Waltzing with Bears' book: https://www.amazon.com/Waltzing-Bears-Managing-Software-Projects/dp/0932633609 ‘Software Estimation' book: https://www.amazon.com/Software-Estimation-Demystifying-Developer-Practices/dp/0735605351 DoomCheck: https://doomcheck.com/ Twitter: @jhbrown94

How long will a project take to complete? How can you get this as close to reality as possible? Software estimation is an essential part of the development process and one that many people don't know how to approach correctly. Is your team equipped with the right tools? Is there a shared understanding of the process within your team? Hosts James Hall (Parallax) and Josh Nesbitt (Stac) explore these questions and look at practical solutions to get it right. Topics covered in this episode: - Mapping the user experience - Demystifying the quote process with the client - Understanding your team and the time estimates they give you - Setting expectations - Internal communication and the quote process - Making tradeoff decisions - Adapting the tools you use as a team - Reusing code - Time management with client tweaks - Previous project analysis - The cost for updating and maintaining a project in the future - Early understanding of the client's system - Building trust - Keeping devs on track via meetings - Creating a shared understanding between front and back-end developers - The value of face-to-face communication and more. Find our more about Stac and Parallax Stac: https://stac.works Parallax: https://parall.ax Resources Planning Poker: https://en.wikipedia.org/wiki/Planning_poker

Show notes 项目预估的方法 分解成更好估计的子项目 确定做项目的顺序：重要性，不确定性，外组依赖，RFC批准 Ramp up流程 对外组需求询问给出粗略估计 更改项目原先预估的时间 不要乐观估计，也不要觉得可以通过加班来按时完成项目 计入ramp步骤时间（diff，launch approval，etc），ramp的过程中开始计划下一个项目 每周更新进度是否正常 联系方式： 官网: eng.cafe 微信公众号: Eng Cafe Twitter: @engcafefm Youtube: Eng Cafe Bilibili 喜马拉雅 小宇宙播客 泛用型播客客户端: eng.cafe/subscribe Email: hi@eng.cafe

1.) People can estimate well what they have done many times before.  2.) Software developers automate what is repetitive or time consuming.  3.) To estimate something well one must have repeated it many times before and not automated it.  4.) Why would a software developer not automate something repeated many times before?  Join Chris and Austin as they discuss and grapple with this paradox.   Video and show notes: https://youtu.be/woF8lkhxKgc 

For the past year, Steve McConnell has applied his extensive estimation expertise to a timely problem: Covid-19 forecasting. Steve’s Covid Complete Data Center provides US national data, state data for every state, state scorecards, forecasts, forecast evaluations, and other data on the pandemic: https://stevemcconnell.com/covidcomplete/ His Covid Complete forecasting model has been accepted into the US Center for Disease Control’s “Ensemble” model, which means that it is one of the models driving overall CDC forecasting. In this episode, host Mark Griffin and Steve explore what Steve has learned from his modeling efforts and the lessons learned that are valuable for the software world. You’ll learn the importance of the following for software estimation: using historical data, keeping "control knobs" to a minimum, the difference between accuracy and precision, the difference between reported and actual ground truth, and the absolute necessity of closing the loop and judging your forecasts’ accuracy and effectiveness.

We thought we’d do something fun to start our second season and use a familiar vehicle to help new listeners and our old friends understand Construx’s software engineering expertise. And how are we going to do that? We’re going to use beer! You might be thinking, "Well, now you have my attention." Host Mark Griffin and Construx consultant Steve Tockey are accomplished home brewers, with 39 years of beer-brewing experience between them. In this first part of the conversation, they’ll work through the beginning phases of software development—requirements, design, and estimation—choosing beers that pair well with each phase, given the similar desired outcome of the particular beer and the software phase. Learn, for example, how software design is similar to an English IPA. We’re pretty sure you’ve never heard anything quite like this.

This month on the Cucumber Podcast, Seb Rose and Matt Wynne speak to George Dinwiddie, an old friend of the pod and author of a new book "Software Estimation without Guessing". Buy George's book "Software Estimation without Guessing" - https://pragprog.com/titles/gdestimate/ Also mentioned "Thanks for the feedback" by Sheila Heen and Douglas Stone. https://www.penguinrandomhouse.com/books/313485/thanks-for-the-feedback-by-douglas-stone-and-sheila-heen/ Follow George on Twitter - https://twitter.com/gdinwiddie

In this episode, Justyna and Paul talk with George Dinwiddie, the author of Software Estimation without Guessing: Effective Planning in an Imperfect World. And guess what? Mostly we talk about people, not estimating. Get the bookSupport the show (http://patreon.com/agilebookclub)

This week, Dan Neumann is joined by George Dinwiddie, an Independent Software Consultant and Coach who works with organizations both large and small to develop software more effectively. He strives to help organizations, managers, and teams solve the problems they face by providing consulting, coaching, mentoring, and training at all levels.   Dan and George will be taking a deep dive into George’s newest book, Software Estimation Without Guessing: Effective Planning in an Imperfect World, which addresses both the technical and sociological aspects of estimation. In this episode, George takes listeners through several chapters of the book, key points and best practices, as well as myths and misconceptions, all to help your organization achieve its desired goals with less drama and more benefit!   Key Takeaways What is software estimation? A tool to estimate for the particular need you and your organization has Estimation in comparison to past experience and by modeling the work mathematically (or a hybrid of both) One of the big purposes of making estimates is for the business to build a look ahead and make decisions What are not estimations? Commitments Negotiations Plans “Estimations are wrong; if they were right, they would be called measurements.” How to estimate/estimation best practices: It’s important to track progress with your estimates to create a feedback loop (burn up charts are an easy way to do this) It’s okay to be wrong in the estimates With sprints, you want to be more 50/50 with the estimates Communication is critical Having contingency plans in place is a good idea Estimations are not the same as plans — estimate, and if it is critical, then put in some contingency buffers Allow for some space for the unexpected When you find out that your estimate is wrong then that means some assumption that you’ve based your estimation on is wrong (so there’s a lot of value in analyzing what assumption is untrue and to learn from it) For simple estimations (like how much work to take on for the next two weeks) you don’t need a lot of precision or accuracy Set near-term estimates Be clear about how far along you are (“...otherwise, you’ll be fooling yourself”) Have a good measure of what is done or not (you can use test automation for this) A model can be very helpful but if it doesn’t really track reality then it’s going to lead you astray The book’s purpose: It strives to help people work with estimates (given a desire to have things come out well) Provides a guide for comparison-based estimates It’s not very recipe-driven; it more so provides things to think about and options to consider A how-to on estimating for unknowns Rather than walking people through a series of steps, George’s book aims to help people think about what they’re trying to accomplish and how what they’re doing is accomplishing that Approaches to estimation: Enlisting Expert Estimators  Using a model such as the COCOMO model (which is encoding how you compare it to other experiences) Utilizing function points Notes about the social side of estimation: Having in-person communication skills are just as important as your programming skills The better you can balance a concern for the needs of self, the needs of the other, and the needs of the context, the better things will be (even if the other person is not doing a good job of balancing them)   Mentioned in this Episode: George Dinwiddie Software Estimation Without Guessing: Effective Planning in an Imperfect World, by George Dinwiddie Agile Estimating and Planning, by Mike Cohn Planning PokerFibonacci Sequence Agile2020 Conference James Grenning Software Estimation: Demystifying the Black Art (Developer Best Practices), by Steve McConnell COCOMO Model Burn Up Chart Gerald Weinberg Donald Rumsfeld — Unknown Unknowns Virginia Satir’s Concept of Congruence The Fifth Discipline: The Art & Practice of The Learning Organization, by Peter M. Senge   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

Get the book: https://pragprog.com/book/gdestimate/software-estimation-without-guessingFollow Agile Book Club for discounts on books and other goodies:FacebookTwitterYouTubeLinkedInInstagramSupport the show (http://patreon.com/agilebookclub)

Welcome to the Software Estimation and Quality Podcast! This is a brief introduction to our show. Please visit our web site, http://www.namcook.com/podcasts for further information.

It’s human nature that businesses have a desire for software estimation. For projects with a fixed scope, typical estimating methods can be off by as much as 70%. And that’s a product that doesn’t adapt to user needs. If you desire the economic growth that comes from building winning products for customers, the numbers will be even worse. The short of it? Don’t bother! Pick a budget for what you can afford each month, and let a qualified development team or consultancy tell you if they can build a minimum viable product (MVP) in 1/6th to 1/12th of that budget. This will produce your core theory of value and two delighting features early, with monthly budget left over to adapt to changes. If you find that the product needs to change spend some budget on those changes. If you find that the product needs to improve in quality, spend some budget on beefing up testing. Software projects don’t fail because the product couldn’t get built in time – they fail because they DON'T DELIVER VALUE high enough to justify the investment. To reach this high level of value means spending less time envisioning, and more time ADAPTING. The only way to do this is with a laser focus on the core theory of value, and a budget that will last through several feedback cycles. Any time a product owner/manager or non-technical person of any sort asks for an estimate, they create anxiety in those doing the work. Experienced technologists know the number of variables in software development is ridiculous, and systems that have been created so far to account for all possible outcomes fall far short of being helpful. Though we may need to estimate whether we can deliver the core theory of value within a time frame short enough to get feedback, ongoing estimation should be unnecessary if budgeting of software is done on a subscription-based, value-focused basis. Software businesses must ensure that insights about how the product is being used are recorded with every release of the product. Minimal change must be introduced each release, to allow for A/B testing to determine whether a change had the desired impact on business outcomes. How business outcomes are measured is specific to each business, but these must be determined and agreed upon BEFORE development of any feature that will impact them starts. The effort of a successful software project focuses on measuring whether each release is getting the business CLOSER TO AN OUTCOME, not closer to completing a FIXED SCOPE OF WORK! This paradox can be hard to wrap your head around, but it must be fully appreciated to operate in a truly lean fashion. Determine what you can spend per month, get started, and adapt… TRUST THE MARKET, not your ego! You can also watch this episode on YouTube.  Related resources: Principles of Product Development Flow (Amazon) Minimum Viable Product - Letting Software Companies Help You Profit Agile Project Management - Is It Stopping You From Being Agile? Lean Software Development - It's About Uncertainty!   Visit me at JaymeEdwards.com Find me on Facebook at JaymeEdwardsMedia Find me on Twitter as @jaymeedwards

Steve McConnell (@stevemconstrux) joined me (@RyanRipley) to discuss #NoEstimates, how estimates help teams collaborate with stakeholders, and what professional estimation looks like on an agile team. [featured-image single_newwindow=”false”]Steve McConnell – CEO of Construx[/featured-image] Steve is the CEO of Construx Software. He is the author of many award winning books including:  Code Complete, Rapid Software Development, and Software Estimation: Demystifying the Black Art. He blogs at 10x Software Development and widely acknowledged as a thought leader in estimation, software requirements, and software development. In this episode you'll discover: A critical view of #NoEstimates concepts How estimation can help foster collaboration between stakeholders and developers What estimation practices looks like in the context of a Scrum team Strategies you can use to avoid bad estimation practices Links from the show: Steve’s Brain Cast Video on #NoEstimates 1st Response to Steve’s Video by Ron Jeffries Steve’s 17 Theses on Software Estimation Ron Jeffries Response to the 17 Theses On-Demand Training Courses from Steve and Construx [callout]Often referred to as the “black art” because of its complexity and uncertainty, software estimation is not as difficult or puzzling as people think. In fact, generating accurate estimates is straightforward—once you understand the art of creating them. In his highly anticipated book, acclaimed author Steve McConnell unravels the mystery to successful software estimation—distilling academic information and real-world experience into a practical guide for working software professionals. Click here to purchase on Amazon.[/callout] [reminder]What are your views on #NoEstimates and Estimation? Please let us know in comments section below.[/reminder] Want to hear about the life of an agile coach? — Listen to my conversation with Zach Bonaker, Diane Zajac-Woodie, and Amitai Schlair on episode 39. We discuss growing an agile practice and how coaches help create the environments where agile ideas can flourish. One tiny favor.  — Please take 30 seconds now and leave a review on iTunes. This helps others learn about the show and grows our audience. It will help the show tremendously, including my ability to bring on more great guests for all of us to learn from. Thanks! This podcast is brought to you by Audible. I have used Audible for years, and I love audio books. I have three to recommend: Agile and Lean Program Management by Johanna Rothman Scrum: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland The Lean Startup by Eric Ries All you need to do to get your free 30-day Audible trial is go to Audibletrial.com/agile. Choose one of the above books, or choose between more than 180,000 audio programs. It's that easy. Go to Audibletrial.com/agile and get started today. Enjoy! The post AFH 052: Software Estimation with Steve McConnell [PODCAST] appeared first on Ryan Ripley.See omnystudio.com/listener for privacy information.

Sven Johann talks with Steve McConnell about Software Estimation. Topics include when and why businesses need estimates and when they don’t need them; turning estimates into a plan and validating progress on the plan; why software estimates are always full of uncertainties, what these uncertainties are and how to deal with them. They continue with: […]

Sven Johann talks with Steve McConnell about Software Estimation. Topics include when and why businesses need estimates and when they don’t need them; turning estimates into a plan and validating progress on the plan; why software estimates are always full of uncertainties, what these uncertainties are and how to deal with them. They continue with: estimation, planning and monitoring a Scrum project from the beginning to a possible end. They close with estimation techniques in the large (counting, empirical data) and in the small (e.g. poker planning).

Software Estimation is Hard Fist-to-Five Estimation Agile / Waterfall Methodologies Scope Creep Minecraft Creeper YAGNI

Matt and Andy dive into their first "real" topic - how do you estimate the cost to build software?

Welcome to the Software Process and Measurement Cast 190! The SPaMCAST 190 features my interview with Raja Bavani. We discussed distributed agile! Raja Bavani is Chief Architect of MindTree’s Product Engineering Services (PES) and IT Services (ITS) groups and plays the role of agile evangelist. He has more than 20 years of experience in the IT industry and has published papers at international conferences on topics related to Code Quality, Distributed Agile, Customer Value Management and Software Estimation.  His IT experience started during the early 90s, when he was involved in porting a leading ERP product across various UNIX platforms. Later he moved onto products that involved data mining and master data management. During early 2000, he worked with some of the niche independent software vendors in the hospitality and finance domains.  At MindTree, he has worked with some of the top vendors of virtualization platforms, business service management solutions and health care products.  His areas of interests include Global Delivery Model, Agile Software Development, Requirements Engineering, Software Architecture, Software Reuse, Customer Value Management, Knowledge Management, and IT Outsourcing.  He is a member of IEEE and IEEE Computer Society.  He regularly interfaces with educational institutions to offer guest lectures and writes for technical conferences.  Also, he writes for magazines such as Agile Record, Cutter IT Journal and SD Times.   He blogs on Distributed Agile at http://www.mindtree.com/blogs/author/raja-bavani Raja's blog on Software Engineering and his articles and white papers are available at http://se-thoughtograph.blogspot.com He can be reached at raja_bavani@mindtree.com Shameless Ad for my book!  Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: "This book will prove that software projects should not be a tedious process, neither for you or your team." News just in  . . . We also just got word that the SPM book has been adopted for a class at the University of West Flroida for the Fall. Have you bought your copy? Contact information for the Software Process and Measurement CastEmail:  spamcastinfo@gmail.comVoicemail:  +1-206-888-6111Website: www.spamcast.netTwitter: www.twitter.com/tcagleyFacebook:  http://bit.ly/16fBWV Next The Software Process and Measurement Cast 191 will return to my essay "Who Owns Agile Estimation."

Welcome to the Software Process and Measurement Cast 140! SPaMCAST 140 features my interview with Raja Bavani.  We talked about his great article "The ten best influences on software product engineering." The article was originally publised in the SDTime  This was a wide ranging interview went beyond influences and wrestles with the future!   Raja Bavani is Technical Director of MindTree’s Product Engineering Services (PES) group and plays the role of Product Engineering Evangelist and Agile Coach. He has more than 20 years of experience in the IT industry and has published papers at international conferences on topics related to Code Quality, Distributed Agile, Customer Value Management and Software Estimation. His PES experience started during the early 90s, when he was involved in porting a leading ERP product across various UNIX platforms. Later he moved onto products that involved data mining and master data management. During early 2000, he worked with some of the niche independent software vendors in the hospitality and finance domains.  At MindTree, he has worked with some of the top vendors of virtualization platforms, business service management solutions and health care products.  His areas of interests include Global Delivery Model, Agile Software Development, Requirements Engineering, Software Architecture, Software Reuse, Customer Value Management, Knowledge Management, and IT Outsourcing.  He is a member of IEEE and IEEE Computer Society.  He regularly interfaces with educational institutions to offer guest lectures and writes for technical conferences. His Product Engineering blog is available at http://www.mindtree.com/blogs/category/software-product-engineeringHis articles and white papers on Agile Software Development are available at: http://mindtree.com/category/tags/agileHe can be reached at raja_bavani@mindtree.comRaja's personal blog -  http://se-thoughtograph.blogspot.com  Shameless Ad for my book!  Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received great unsolicited reviews and the book has been picked up as a text book for university level work.  Have you bought your copy? Contact information for the Software Process and Measurement CastEmail:  spamcastinfo@gmail.comVoicemail:  +1-206-888-6111Website: www.spamcast.netTwitter: www.twitter.com/tcagleyFacebook:  http://bit.ly/16fBWV Next! So you want to go agile . . .in the SPaMCAST 141 I will present a simple checklist of factors you need to deal with as you progress with change.