PE $1-2.$ As noted in this chapter, software projects fail all too frequently. Read the article $$IT Project Management: Infamous Failures, Classic Mistakes, and Best Practices,$$ by R$.$ Ryan Nelson $(2007$; full publication information provided in the reference list at the end of this chapter$).$ This article provides overviews of several major project failures, including the fundamental reasons each failed. In particular, in that article, focus on Table $2,$Ranking of Classic Mistakes.$$ This table indicates the most frequent reasons that projects fail. In that table, consider how many of these reasons pertain to problems with software construction $($software defects or bugs, poor software performance, frequent crashes$)$ versus problems with software requirements and project management. Which of these predominate? What are the implications for the importance of the BA role?PE $1-2.$ As noted in this chapter, software projects fail all too frequently. Read the article $$IT Project Management: Infamous Failures, Classic Mistakes, and Best Practices,$$ by R$.$ Ryan Nelson $(2007$; full publication information provided in the reference list at the end of this chapter$).$ This article provides overviews of several major project failures, including the fundamental reasons each failed. In particular, in that article, focus on Table $2,$Ranking of Classic Mistakes.$$ This table indicates the most frequent reasons that projects fail. In that table, consider how many of these reasons pertain to problems with software construction $($software defects or bugs, poor software performance, frequent crashes$)$ versus problems with software requirements and project management. Which of these predominate? What are the implications for the importance of the BA role?