References

Achimugu, Philip, Ali Selamat, Roliana Ibrahim, and Mohd Naz’ri Mahrin. 2014. “A systematic literature review of software requirements prioritization research.” Information and Software Technology 56(6):568-585.

ACM. 1999. “The Software Engineering Code of Ethics and Professional Practice.” Association for Computing Machinery and IEEE Computer Society. https://ethics.acm.org/code-of-ethics/software-engineering-code.

Ageling, Willem-Jan. 2020. “Here’s Why Many Developers Hate Scrum.” https://medium.com/serious-scrum/here-is-why-many-developers-hate-scrum-3a43baa015d1.

Agile Alliance. 2021a. “Definition of Done.” https://www.agilealliance.org/glossary/definition-of-done.

Agile Alliance. 2021b. “Acceptance Testing.” https://www.agilealliance.org/glossary/acceptance.

Agile Alliance. 2021c. “12 Principles Behind the Agile Manifesto.” https://www.agilealliance.org/agile101/12-principles-behind-the-agile-manifesto.

Agile Alliance, Jutta Eckstein, and John Buck. 2021. “Changing the Culture by Changing Habits.” https://www.agilealliance.org/changing-the-culture-by-changing-habits.

Aleshire, Peter. 2004. Eye of the Viper: The Making of an F-16 Pilot. Guilford, CT: Lyons Press.

Ambler, Scott W. 2005. The Elements of UML 2.0 Style. New York: Cambridge University Press.

Ambler, Scott W. 2006. “Why Agile Software Development Techniques Work: Improved Feedback.” https://www.ambysoft.com/essays/whyAgileWorksFeedback.html.

American Society for Quality. 2021a. “Quality Glossary - Q.” https://asq.org/quality-resources/quality-glossary/q.

American Society for Quality. 2021b. “Joseph M. Juran.” https://asq.org/about-asq/honorary-members/juran.

American Society for Quality. 2021c. “Cost of Quality (COQ).” https://asq.org/quality-resources/cost-of-quality.

American Society for Quality. 2021d. “What is the Plan-Do-Check-Act (PDCA) Cycle?” https://asq.org/quality-resources/pdca-cycle.

Atwood, Jeff. 2006. “The Programmer’s Bill of Rights.” https://blog.codinghorror.com/the-programmers-bill-of-rights.

Bakker, Jeffrey. 2020. “Top lessons learned from working with a 10x developer.” https://levelup.gitconnected.com/top-lessons-learned-from-working-with-a-10x-developer-51de12383e25.

Barlas, Stephen. 1996. “Anatomy of a Runaway: What Grounded the AAS.” IEEE Software 13(1):104-106.

Beatty, Joy, and Anthony Chen. 2012. Visual Models for Software Requirements. Redmond, WA: Microsoft Press.

Beck, Kent, et al. 2001. “Manifesto for Agile Software Development.” https://agilemanifesto.org.

Beck, Kent. 2003. Test-Driven Development: By Example. Boston: Addison-Wesley.

Beck, Kent, and Cynthia Andres. 2005. Extreme Programming Explained: Embrace Change, 2nd Ed. Boston: Addison-Wesley.

Bentley, Jon. Programming Pearls, 2nd Ed. 2000. Boston: Addison-Wesley.

Booch, Grady, James Rumbaugh, and Ivar Jacobson. 1999. The Unified Modeling Language User Guide. Reading, MA: Addison-Wesley.

Bright Hub PM. 2009. “Various Kinds of Risks Associated with Software Project Management.” https://www.brighthubpm.com/risk-management/47932-risks-involved-in-software-project-management.

Briski, Kari Ann, Poonam Chitale, Valerie Hamilton, Allan Pratt, Brian Starr, Jim Veroulis, and Bruce Villard. 2008. “Minimizing code defects to improve software quality and lower development costs.” IBM Development Solutions Whitepaper. ftp://ftp.software.ibm.com/software/rational/info/do-more/RAW14109USEN.pdf.

Brooks Jr., Frederick P. 1996. The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition. Reading, MA: Addison-Wesley.

Brosseau, Jim. 2008. Software Teamwork: Taking Ownership for Success.Boston: Addison-Wesley.

Brössler, Peter. 1999. “Knowledge management at a software house: An experience report.” In: Ruhe G., Bomarius F. (eds) Learning Software Organizations. SEKE 1999. Lecture Notes in Computer Science, vol 1756. Springer, Berlin, Heidelberg. https://doi.org/10.1007/BFb0101419.

Charette, Robert N. 1996. “Large-Scale Project Management Is Risk Management.” IEEE Software 13(4):110-117.

Charette, Robert N. 2005. “Why Software Fails.” IEEE Spectrum. 42(9):42-49 https://spectrum.ieee.org/computing/software/why-software-fails.

Chrissis, Mary Beth, Mike Konrad, and Sandy Shrum. 2003. CMMI: Guidelines for Process Integration and Product Improvement. Boston: Addison-Wesley.

CMMI Institute. 2017. “Published Appraisal Results.” https://cmmiinstitute.com/pars.

Cohen, Esther. 2018. “How to Use the Critical Path Method for Complete Beginners.” https://www.workamajig.com/blog/critical-path-method.

Cohn, Mike. 2004. User Stories Applied: For Agile Software Development. Boston: Addison-Wesley.

Cohn, Mike.. 2006. Agile Estimating and Planning. Boston: Addison-Wesley.

Cohn, Mike.. 2010. Succeeding with Agile: Software Development Using Scrum. Boston: Addison-Wesley.

Cohn, Mike.. 2014. “Know Exactly What Velocity Means to Your Scrum Team.” https://www.mountaingoatsoftware.com/blog/know-exactly-what-velocity-means-to-your-scrum-team.

Coleman, Ben, and Dan Goodwin. 2017. Designing UX: Prototyping. Collingwood, VIC, Australia: SitePoint Pty. Ltd.

Colorado State University. n.d. “Survey Research.” https://writing.colostate.edu/guides/guide.cfm?guideid=68.

Constantine, Larry L., and Lucy A.D. Lockwood. 1999. Software for Use: A Practical Guide to the Models and Methods of Usage-Centered Design. Reading, MA: Addison-Wesley.

Construx. 2010a. “Individual Productivity Variation in Software Development.” https://www.construx.com/blog/productivity-variations-among-software-developers-and-teams-the-origin-of-10x.

Cooper, Alan, Robert Reimann, David Cronin, and Christopher Noessel. 2014. About Face: The Essentials of Interaction Design, 4th ed. Indianapolis, IN: John Wiley & Sons, Inc.

Costello, Katie. 2019. “The Secret to DevOps Success.” Gartner. https://www.gartner.com/smarterwithgartner/the-secret-to-devops-success.

Covey, Stephen R. 2020. The 7 Habits of Highly Effective People, 25th Anniversary Edition. New York: Simon & Schuster.

Crosby, Philip B. 1979. Quality Is Free: The Art of Making Quality Certain. New York: McGraw-Hill.

Cunningham, Ward. 1992. “The WyCash Portfolio Management System.” OOPSLA ‘92 Experience Report. http://c2.com/doc/oopsla92.html.

Datt, Priyanka. 2020a. “Difference Between Product Owner & Business Analyst Role.” https://premieragile.com/difference-between-product-owner-and-business-analyst.

Datt, Priyanka. 2020b. “What is the Definition of Done (DoD) in Agile?” https://premieragile.com/definition-of-done-in-agile.

Davis, Alan M. 1995. 201 Principles of Software Development. New York: McGraw-Hill.

Davis, Alan M. 2005. Just Enough Requirements Management: Where Software Development Meets Marketing. New York: Dorset House Publishing.

DeMarco, Tom. 1979. Structured Analysis and System Specification. Upper Saddle River, NJ: Yourdon Press.

DeMarco, Tom. 2001. Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency. New York: Broadway Books.

DeMarco, Tom, and Timothy Lister. 2003. Waltzing With Bears: Managing Risk on Software Projects. New York: Dorset House Publishing.

DeMarco, Tom, and Timothy Lister. 2013. Peopleware: Productive Projects and Teams, 3rd Ed. Boston: Addison-Wesley.

Derby, Esther, and Diana Larsen. 2006. Agile Retrospectives: Making Good Teams Great. Pragmatic Bookshelf.

DOT. 1998. “Audit Report: Advance Automation System, Federal Aviation Administration Report Number AV-1998-113.” Washington, DC: Office of Inspector General, U.S. Department of Transportation.

Feldmann, Clarence G. 1998. The Practical Guide to Business Process Reengineering Using IDEF0. New York: Dorset House Publishing.

Fisher, Roger, William Ury, and Bruce Patton. 2011. Getting to Yes: Negotiating Agreement Without Giving In, 3rd Ed. New York: Penguin Books.

Foord, Michael. 2017. “30 best practices for software development and testing.” https://opensource.com/article/17/5/30-best-practices-software-development-and-testing.

Gamma, Erich, Richard Helm, Ralph Johnson, and John Vlissides. 1995. Design Patterns: Elements of Reusable Object-Oriented Software. Reading, MA: Addison-Wesley.

Gilb, Tom. 2005. Competitive Engineering: A Handbook for Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage. Oxford, England: Elsevier Butterworth-Heinemann.

Gilb, Tom, and Dorothy Graham. 1993. Software Inspection. Reading, MA: Addison-Wesley.

Glass, Robert L. 2003. Facts and Fallacies of Software Engineering. Boston: Addison-Wesley.

Goldratt, Eliyahu M. 1997. Critical Chain. Great Barrington, MA: The North River Press.

Gottesdiener, Ellen. 2002. Requirements by Collaboration: Workshops for Defining Needs. Boston: Addison-Wesley.

Grady, Robert B. 1999. “An Economic Release Decision Model: Insights into Software Project Management.” In Proceedings of the Applications of Software Measurement Conference, 227–239. Orange Park, FL: Software Quality Engineering.

Grady, Robert B., and Tom Van Slack. 1994. “Key Lessons in Achieving Widespread Inspection Use.” IEEE Software 11(4):46–57.

Gray, Mark. 2020. “Is the Way You Use Burndown Charts Helping or Holding You Back?” https://medium.com/better-programming/the-definitive-guide-to-burn-down-charts-a176db096294.

Hasan, Mohammad Shabbir, Abdullah Al Mahmood, Md. Jahangir Alam, Sk. Md. Nahid Hasan, and Farin Rahman. 2010. “An Evaluation of Software Requirement Prioritization Techniques.” International Journal of Computer Science and Information Security 8(9):83-94.

Haskins, B., J. Stecklein, D. Brandon, G. Moroney, R. Lovell, and J. Dabney. 2004. ‘‘Error Cost Escalation through the Project Life Cycle.’’ In Proceedings of the 14th Annual International Symposium of INCOSE, 1723–1737. Toulouse, France. International Council on Systems Engineering.

Hatch, Nan. 2019. “10 Critical Culture Change Elements in Agile Transformation.” https://www.insight.com/en_US/content-and-resources/blog/10-critical-culture-change-elements-in-agile-transformation.html.

Hilliard, Andy. 2018. “A Look At Software Development Culture.” https://www.accelerance.com/blog/software-development-culture.

Holland, Dick. 1999. “Document Inspection as an Agent of Change.” Software Quality Professional 2(1):22-33.

Hossain, Md. Shahadat. 2018. “Rework and Reuse Effects in Software Economy.” Global Journal of Computer Science and Technology (C): Software & Data Engineering 18(4-C):35-50. https://globaljournals.org/GJCST_Volume18/5-Rework-and-Reuse-Effects.pdf.

IIBA. 2015. A Guide to the Business Analysis Body of Knowledge (BABOK Guide), 3rd Ed. Toronto, ON, Canada: International Institute of Business Analysis.

ISO/IEC. 2011. ISO/IEC 25010:2011(en) Systems and software engineering—Systems and software Quality Requirements and Evaluation (SQuaRE)—System and software quality models. https://www.iso.org/obp/ui/#iso:std:iso-iec:25010:ed-1:v1:en.

ISO/IEC/IEEE. 2018. ISO/IEC/IEEE 29148:2018 Systems and software engineering—Life cycle processes—Requirements engineering. https://www.iso.org/standard/72089.html.

Jones, Capers. 1994. Assessment and Control of Software Risks. Upper Saddle River, NJ: Yourdon Press.

Jones, Capers. 2006. “Social and Technical Reasons for Software Project Failures.” CrossTalk 19(6):4–9. https://apps.dtic.mil/dtic/tr/fulltext/u2/a487371.pdf.

Juran. 2019. “Features of Quality & Definition of Quality Excellence.” https://www.juran.com/blog/features-of-quality-definition-of-quality-excellence.

Kaley, Anna. 2021. “Mapping User Stories in Agile.” https://www.nngroup.com/articles/user-story-mapping.

Kaner, Cem, James Bach, and Bret Pettichord. 2002. Lessons Learned in Software Testing: A Context-Driven Approach. New York: John Wiley & Sons.

Karten, Naomi. 1994. Managing Expectations: Working with People Who Want More, Better, Faster, Sooner, NOW! New York: Dorset House Publishing.

Kerievsky, Joshua. 2005. Refactoring to Patterns. Boston: Addison-Wesley.

Kerth, Norman L. 2001. Project Retrospectives: a Handbook for Team Reviews. New York: Dorset House Publishing.

Klement, Alan. 2013. “Replacing The User Story With the Job Story.” https://jtbd.info/replacing-the-user-story-with-the-job-story-af7cdee10c27.

Koopman, Philip. 2010. Better Embedded System Software. Pittsburgh, PA: Drumnadrochit Press.

Krasner, Herb. 2018. “The Cost of Poor Quality Software in the US: A 2018 Report.” Consortium for IT Software Quality. https://www.it-cisq.org/the-cost-of-poor-quality-software-in-the-us-a-2018-report/The-Cost-of-Poor-Quality-Software-in-the-US-2018-Report.pdf.

Kukreja, Nupul, Barry Boehm, Sheetal Swaroop Payyavula, and Srinivas Padmanabhuni. 2012. “Selecting an Appropriate Framework for Value-Based Requirements Prioritization.” In Proceedings of the 2012 20th IEEE International Requirements Engineering Conference, 303–308. Los Alamitos, CA: IEEE Computer Society Press.

Kulak, Daryl, and Eamonn Guiney. 2004. Use Cases: Requirements in Context, 2nd Ed. Boston: Addison-Wesley.

Larman, Craig. 2004. Agile and Iterative Development: A Manager’s Guide. Boston: Addison-Wesley.

Leffingwell, Dean. 2011. Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise. Boston: Addison-Wesley.

Leonard, Andrew. 2020. “Committing to collaboration.” https://increment.com/remote/committing-to-collaboration-version-control.

Löwe, Nils. 2015. “Our Responsibility as Software Developers.” https://www.infoq.com/articles/Responsible-Software-Development.

Lucidchart. 2021. “How to perform a stakeholder analysis.” https://www.lucidchart.com/blog/how-to-do-a-stakeholder-analysis.

MacKay, Jory. 2021. “Context switching: Why jumping between tasks is killing your productivity (and what you can do about it).” https://blog.rescuetime.com/context-switching.

Mancuso, Sandro. 2016. “Cohesion—The cornerstone of Software Design.” https://www.codurance.com/publications/software-creation/2016/03/03/cohesion-cornerstone-software-design.

Manns, Mary Lynn, and Linda Rising. 2005. Fearless Change: Patterns for Introducing New Ideas. Boston: Addison-Wesley.

Marasco, Joe. 2007. “What Is the Cost of a Requirement Error?” https://www.stickyminds.com/article/what-cost-requirement-error.

Mathieson, SA. 2019. “How diversity spurs creativity in software development.” https://www.computerweekly.com/feature/How-diversity-spurs-creativity-in-software-development.

McAllister, David. 2017. “Software Waste & The Cost of Rework.” https://www.linkedin.com/pulse/software-waste-cost-rework-david-mcallister.

McConnell, Steve. 1996. Rapid Development: Taming Wild Software Schedules. Redmond, WA: Microsoft Press.

McConnell, Steve. 2004. Code Complete: A Practical Handbook of Software Construction, 2nd Ed. Redmond, WA: Microsoft Press.

McConnell, Steve. 2006. Software Estimation: Demystifying the Black Art. Redmond, WA: Microsoft Press.

McConnell, Steve. 2010. “Origins of 10X—How Valid is the Underlying Research?” https://www.construx.com/blog/the-origins-of-10x-how-valid-is-the-underlying-research.

McGreal, Don, and Ralph Jocham. 2018. The Professional Product Owner: Leveraging Scrum as a Competitive Advantage. Boston: Addison-Wesley.

McMenamin, Steve, Tom DeMarco, Peter Hruschka, Tim Lister, James Robertson, and Suzanne Robertson. 2021. Happy to Work Here: Understanding and Improving the Culture at Work. New Atlantic.

McPeak, Alex. 2017. “What’s the True Cost of a Software Bug?” https://smartbear.com/blog/software-bug-cost.

Merrill, Cache. 2019. “Software Maintenance: Understanding the 4 Main Types.” https://www.zibtek.com/blog/software-maintenance-understanding-the-4-main-types.

Microsoft. 2017. “SQL Injection.” https://docs.microsoft.com/en-us/sql/relational-databases/security/sql-injection.

Miller, Roxanne E. 2009. The Quest for Software Requirements. Milwaukee, WI: MavenMark Books.

Minott, Zachary. 2020. “How I Outperformed More Experienced Developers as a Junior Developer (and How You Can Too).” https://medium.com/better-programming/how-i-outperformed-more-experienced-developers-as-a-junior-developer-and-how-you-can-too-19bc6206fa68.

Moore, Geoffrey A. 2014. Crossing the Chasm: Marketing and Selling Disruptive Products to Mainstream Customers, 3rd Ed. New York: HarperBusiness.

Musa, J.D. 1993. “Operational profiles in software-reliability engineering.” IEEE Software 10(2):14-32.

Nagappan, Raj. 2020a. “Moving beyond user story templates.” https://uxdesign.cc/moving-beyond-user-story-templates-79a421c6445c.

Nagappan, Raj. 2020b. “The iron triangle and Agile.” https://uxdesign.cc/the-iron-triangle-and-agile-7b66d3c72a51.

Nielsen, Jakob. 2020. “10 Usability Heuristics for User Interface Design.” https://www.nngroup.com/articles/ten-usability-heuristics.

Nichols, Bill. 2020. “Programmer Moneyball: Challenging the Myth of Individual Programmer Productivity.” https://insights.sei.cmu.edu/sei_blog/2020/01/programmer-moneyball-challenging-the-myth-of-individual-programmer-productivity.html.

NIST. 2002. “Planning Report 02-3. The Economic Impacts of Inadequate Infrastructure for Software Testing.” National Institute of Standards & Technology. https://www.nist.gov/system/files/documents/director/planning/report02-3.pdf.

Nussbaum, Hillary. 2020. “Rework is Costing Your Company Millions—It’s Time to Cut Back.” https://codeclimate.com/blog/rework-costs-millions.

Page-Jones, Meilir. 1988. The Practical Guide to Structured Systems Design, 2nd Ed. Englewood Cliffs, NJ: Prentice Hall.

Page-Jones, Meilir. 2000. Fundamentals of Object-Oriented Design in UML. Boston: Addison-Wesley.

Paulk, Mark C., Charles V. Weber, Bill Curtis, and Mary Beth Chrissis. 1995. The Capability Maturity Model: Guidelines for Improving the Software Process. Reading, MA: Addison-Wesley.

Pearls of Wisdom. 2014a. “PEARL XIX: Effective steps to reduce technical debt: An agile approach.” https://agilepearls.wordpress.com/tag/technical-debt.

Pearls of Wisdom. 2014b. “PEARL XXIII: Guidelines for Successful and Effective Retrospectives.” https://agilepearls.wordpress.com/2014/05/23/pearl-xxii-guidelines-for-successful-and-effective-retrospectives.

PMI. n.d. “What is Project Management?” Project Management Institute. https://www.pmi.org/about/learn-about-pmi/what-is-project-management.

PMI. n.d. 2017. “PMI’s Pulse of the Profession 2017: 9th Global Project Management Survey.” http://www.pmi.org/-/media/pmi/documents/public/pdf/learning/thought-leadership/pulse/pulse-of-the-profession-2017.pdf.

Podeswa, Howard. 2009. The Business Analyst’s Handbook. Boston, MA: Course Technology.

Podeswa, Howard. 2021. The Agile Guide to Business Analysis and Planning: From Strategic Plan to Continuous Value Delivery. Boston: Addison-Wesley.

Potter, Neil, and Mary Sakry. 2002. Making Process Improvement Work. Boston: Addison-Wesley.

Praxis. 2019. “Shewhart cycle.” https://www.praxisframework.org/en/library/shewhart-cycle.

Pronschinske, Mitch. 2017. “Lessons from 7 highly successful software engineering cultures.” https://techbeacon.com/app-dev-testing/lessons-7-highly-successful-software-engineering-cultures.

Pugh, Ken. 2005. Prefactoring: Extreme Abstraction, Extreme Separation, Extreme Readability. Sebastopol, CA: O’Reilly Media, Inc.

Pugh, Ken. 2006. Interface Oriented Design: With Patterns. Pragmatic Bookshelf.

Radice, Ronald A. 2002. High Quality Low Cost Software Inspections. Andover, MA: Paradoxicon Publishing.

Resologics. 2021. “Team agreements: A key to high-performing, happy teams.” https://www.resologics.com/resologics-blog/2017/7/12/team-agreements-a-key-to-high-performing-happy-teams.

Rettig, Marc. 1990. “Software Teams.” Communications of the ACM 33(10):23-27.

Rice, David. 2016. “How to Avoid Brittle Code.” https://www.gocd.org/2016/03/24/how-to-avoid-brittle-code.

Robertson, Suzanne, and James Robertson. 2013. Mastering the Requirements Process: Getting Requirements Right, 3rd Ed.Boston: Addison-Wesley.

Rothman, Johanna. 1999. “How to Use Inch-Pebbles When You Think You Can’t.” https://www.jrothman.com/articles/1999/01/how-to-use-inch-pebbles-when-you-think-you-cant.

Rothman, Johanna. 2000. “What Does It Cost You To Fix A Defect? And Why Should You Care?” https://www.jrothman.com/articles/2000/10/what-does-it-cost-you-to-fix-a-defect-and-why-should-you-care.

Rothman, Johanna. 2004. “Using Inch-Pebbles to Track Project State.” https://www.jrothman.com/articles/2004/02/using-inch-pebbles-to-track-project-state.

Rothman, Johanna. 2012. “Management Myth #1: The Myth of 100% Utilization.” https://www.jrothman.com/articles/2012/01/management-myth-1-the-myth-of-100-utilization.

Rozanski, Nick, and Eoin Woods. 2005. Software Systems Architecture: Working with Stakeholders Using Viewpoints and Perspectives. Boston: Addison-Wesley.

St Augustine’s College. n.d. “Rights and responsibilities of software developers.” https://sddhsc.wordpress.com/hsc/9-1-development-and-impact-of-software-solutions/9-1-1-social-and-ethical-issues/rights-and-responsibilities-of-software-developers.

Sanket. 2019. “The exponential cost of fixing bugs.” https://deepsource.io/blog/exponential-cost-of-fixing-bugs.

Sas, Darius, and Paris Avgeriou. 2020. “Quality attribute trade-offs in the embedded systems industry: an exploratory case study.” Software Qual J 28(2):505–534. https://doi.org/10.1007/s11219-019-09478-x.

Scaled Agile. 2021a. “Iteration Planning.” https://www.scaledagileframework.com/iteration-planning.

Scaled Agile. 2021b. “Agile Architecture in SAFe.” https://www.scaledagileframework.com/agile-architecture.

Scaled Agile. 2021c. “Nonfunctional Requirements.” https://www.scaledagileframework.com/nonfunctional-requirements.

Scaled Agile. 2021d. “Iteration Retrospective.” https://www.scaledagileframework.com/iteration-retrospective.

Schwaber, Ken, and Jeff Sutherland. 2020. “The Scrum Guide: The Definitive Guide to Scrum: The Rules of the Game.” https://www.scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf.

SEI. 2020. “SEI CERT Coding Standards.” https://wiki.sei.cmu.edu/confluence/display/seccode/SEI+CERT+Coding+Standards.

Senycia, Tristan. 2020. “8 Collaboration Tools You Need To Work With Remote Developers.” https://youteam.io/blog/8-tools-you-need-to-work-with-remote-developers.

Shore, James. 2010. “The Art of Agile Development: The Planning Game.” https://www.jamesshore.com/v2/books/aoad1/the_planning_game.

Simmons, Erik. 2001. “Quantifying Quality Requirements Using Planguage.” http://understandingrequirements.com/resources/2.23%20%20Quantifying%20Quality%20Requirements.pdf.

Sliger, Michele. 2012. “Agile estimation techniques.” Paper presented at PMI® Global Congress 2012—North America, Vancouver, BC, Canada. Newtown Square, PA: Project Management Institute. https://www.pmi.org/learning/library/agile-project-estimation-techniques-6110.

Soni, Vishal. 2020. “A Practical Prioritization Approach for Technical Debt.” https://productcoalition.com/a-practical-prioritization-approach-for-technical-debt-f1eb31b8e409.

Spolsky, Joel. 2001. “Human Task Switches Considered Harmful.” https://www.joelonsoftware.com/2001/02/12/human-task-switches-considered-harmful.

StackExchange. n.d. “The Programmers Bill of Responsibilities.” https://softwareengineering.stackexchange.com/questions/29177/the-programmers-bill-of-responsibilities.

Stretton, Alan. 2018. “Relating causes of project failure to an organizational strategic business framework.” PM World Journal, Vol VII, Issue I, January. https://pmworldlibrary.net/wp-content/uploads/2018/01/pmwj66-Jan2018-Stretton-relating-project-failures-to-strategic-framework-featured-paper.pdf.

The American Heritage Dictionary of the English Language. 2020. https://www.ahdictionary.com.

The Mann Group. 2019. “Gentle Pressure, Relentlessly Applied: Agreement on Approach.” https://www.manngroup.net/gentle-pressure-relentlessly-applied-agreement-on-approach.

The Standish Group. 2014. “Exceeding Value.” The Standish Group International, Inc. https://www.standishgroup.com/sample_research_files/Exceeding%20Value_Layout.pdf.

The Standish Group. 2015. “CHAOS Report 2015.” The Standish Group International, Inc. https://standishgroup.com/sample_research_files/CHAOSReport2015-Final.pdf.

Thomas, Steven. 2008a. “Agile Project Scope.” https://itsadeliverything.com/agile-project-scope.

Thomas, Steven. 2008b. “Agile Project Planning.” https://itsadeliverything.com/agile-project-planning.

TutorialsPoint. 2021. “Software Design Basics.” https://www.tutorialspoint.com/software_engineering/software_design_basics.htm.

280 Group. 2021. “Product Manager Roles and Responsibilities.” https://280group.com/what-is-product-management/roles/product-manager.

Visual Paradigm. 2020. “Daily Scrum Meeting—A Quick Guide.” https://www.visual-paradigm.com/scrum/daily-scrum-meeting-quick-guide.

Walker, Bryan, and Sarah A. Soule. 2017. “Changing Company Culture Requires a Movement, Not a Mandate.” https://hbr.org/2017/06/changing-company-culture-requires-a-movement-not-a-mandate.

Weinberg, Gerald. 2012. “Agile and the Definition of Quality.” https://secretsofconsulting.blogspot.com/2012/09/agile-and-definition-of-quality.html.

Weinberger, Matt. 2019. “Where Are They Now? What happened to the people in Microsoft’s iconic 1978 company photo.” https://www.businessinsider.com/microsoft-1978-photo-2016-10.

Wiegers, Karl E. 1989. “The Laws of Computing.” ST-Log, no. 31 (May):97–98. https://www.atarimagazines.com/st-log/issue31/097_1_FOOTNOTES_THE_LAWS_OF_COMPUTING.php.

Wiegers, Karl E. 1996. Creating a Software Engineering Culture. New York: Dorset House Publishing.

Wiegers, Karl E. 1998a. “Know Your Enemy: Software Risk Management.” Software Development 6(10):38-42.

Wiegers, Karl E. 1998b. “Improve Your Process With Online ‘Good Practices’.” Software Development 6(12):45-50.

Wiegers, Karl E. 2002a. Peer Reviews in Software: A Practical Guide. Boston: Addison-Wesley.

Wiegers, Karl E. 2002b. “Karl Wiegers on Humanizing Peer Reviews.” STQE 4(2):22-28. http://www.processimpact.com/articles/humanizing_reviews.pdf.

Wiegers, Karl E. 2003. “See You in Court.” Software Development 11(1):36-40.

Wiegers, Karl E. 2006a. More About Software Requirements: Thorny Issues and Practical Advice. Redmond, WA: Microsoft Press.

Wiegers, Karl E. 2006b. “Estimation Safety Tips.” https://www.stickyminds.com/article/estimation-safety-tips.

Wiegers, Karl E. 2007. Practical Project Initiation: A Handbook with Tools. Redmond, WA: Microsoft Press.

Wiegers, Karl. 2019a. “Why Modeling Is an Essential Business Analysis Technique.” https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/5438/Why-Modeling-Is-an-Essential-Business-Analysis-Technique.aspx.

Wiegers, Karl. 2019b. “Why Is Software Always Ninety Percent Done?” https://medium.com/swlh/why-is-software-always-ninety-percent-done-38e125c8b35c.

Wiegers, Karl. 2019c. “Rethinking the Triple Constraint: Five Project Dimensions.” https://medium.com/swlh/rethinking-the-triple-constraint-five-project-dimensions-b3593c364b11.

Wiegers, Karl. 2019d. “Negotiating Achievable Commitments.” https://medium.com/swlh/negotiating-achievable-commitments-6575b3d73b20.

Wiegers, Karl. 2019e. “Mind the Crap Gap.” https://karlwiegers.medium.com/mind-the-crap-gap-61f314fe9678.

Wiegers, Karl. 2019f. “The Core Question about Building Better Software.” https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/5315/categoryId/35/The-Core-Question-about-Building-Better-Software.aspx.

Wiegers, Karl. 2019g. “Project Retrospectives: Looking Back to Look Ahead.” https://medium.com/swlh/project-retrospectives-looking-back-to-look-ahead-f77ab9d4591c.

Wiegers, Karl. 2021. The Thoughtless Design of Everyday Things. Plantation, FL: J. Ross Publishing.

Wiegers, Karl, and Joy Beatty. 2013. Software Requirements, 3rd Ed. Redmond, WA: Microsoft Press.

Wiegers, Karl, and Joy Beatty. 2016. “Agile Requirements: What’s the Big Deal?” https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/3573/Agile-Requirements-Whats-the-Big-Deal.aspx.

Wikic2. 2006. “Developer Bill Of Responsibilities.” https://wiki.c2.com/?DeveloperBillOfResponsibilities.

Wikic2. 2008. “Developer Bill Of Rights.” https://wiki.c2.com/?DeveloperBillOfRights.

Wikipedia. 2020. “Design for X.” Last modified March 7, 2020. https://en.wikipedia.org/wiki/Design_for_X.

Wikipedia. 2021. “Agile software development.” Last modified April 22, 2021. https://en.wikipedia.org/wiki/Agile_software_development.

Winters, Titus, Tom Manshreck, and Hyrum Wright. 2020. Software Engineering at Google: Lessons Learned from Programming Over Time. Sebastopol, CA: O’Reilly Media, Inc.

Wright, Elizabeth. 2016. “The Cover Oregon Debacle.” Citizens Against Government Waste. https://www.cagw.org/thewastewatcher/cover-oregon-debacle.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
35.175.172.94