BUSA8030 Chap.11 Agile Methods and Bimodal IT for Analytics Projects
Agile Methods and Bimodal IT for Analytics Projects
Week 8 contrasts analytics for business, which focuses on good models with an engineering mindset, with analytics in business, which focuses on business outcomes and treats the system and the work around it as evolving together. The unit sides with the second view, and that choice has consequences for how analytics projects are managed.
A quoted designer warns that teams often start with machine learning as the solution and skip finding a meaningful human problem, ending up with powerful systems for problems that barely exist.
Project management starts from three features of a project: an end point, some novelty and a deliverable.
How to manage it depends on the deliverable, the business context and the team, and above all on whether the problem is clear or blurred. Clear problems allow deliverables to be designed in advance within the iron triangle of quality, time and cost; blurred problems need room for scope to change.
Traditional project management stresses roles, control and deliverables, while agile stresses iteration, flexibility, collaboration and satisfaction, and the lecture insists both are relevant to complex projects.
Agile methods such as Scrum work through iterative, incremental practice and embrace changing requirements.
The agile principles shown in the lecture emphasise early and continuous delivery, welcoming change, frequent working releases, daily collaboration, motivated teams, face-to-face conversation, sustainable pace, technical excellence, simplicity, self-organisation and regular reflection.
Bimodal IT, a Gartner idea, separates a stable traditional mode from a fast experimental agile mode; a reading by Haffke and colleagues identifies four bimodal archetypes and shows firms moving between them. The group project brief allows Jira and Confluence to show project and communication plans.
What this chapter covers
- 01
Analytics for business versus in business
- 02
Starting from the problem, not the tool
- 03
Clear and blurred problems
- 04
Traditional and agile project management
- 05
Agile principles in analytics work
- 06
Bimodal IT and the hand-over
Worked example · free
AskSia practice weighting: choosing a method for each workstream
- 1Workstream (a) has a clear problem and fixed deadline: manage it traditionally with controlled scope.
- 2Workstream (b) has a blurred problem: run short agile cycles with field crews testing each version.
- 1Place (a) in the stable mode and (b) in the experimental mode of bimodal IT.
- 1Plan the hand-over: standards the leak model must meet before joining stable operations.
Key terms
- Agile methods
- Project approaches that deliver in short iterations and embrace changing requirements.
- Scrum
- An agile framework that organises work into iterative, incremental cycles with close collaboration.
- Product backlog
- A prioritised list of work items that an agile team draws from in each cycle.
- Bimodal IT
- An IT model with a stable traditional mode and a fast, experimental agile mode.
- Blurred problem
- A problem whose final deliverable cannot be fully designed in advance.
- Socio-technical view
- A view in which technology and the surrounding work evolve together.
Agile Methods and Bimodal IT for Analytics Projects FAQ
What is the difference between analytics for business and analytics in business?
Analytics for business focuses on building good models with an engineering mindset. Analytics in business focuses on business outcomes and treats the technology and the work around it as evolving together.
When should an analytics project use agile methods?
When the problem is blurred and the final deliverable cannot be designed in advance. Week 8 describes agile as suited to unclear and developmental problems, while clear problems can be planned more traditionally.
Does agile mean there is no project plan?
No. Agile teams plan in short horizons using a prioritised backlog and regular reviews. A proposal still needs a timeline, milestones and resources, even if detailed scope evolves.
What is bimodal IT?
A Gartner idea that splits IT into a traditional mode focused on stability and an agile mode focused on speed and experimentation, helping managers balance governance with innovation.
Can my group use Jira and Confluence?
Yes. The group project brief says Jira may be used for project management and Confluence for team communication, with snapshots included in the slides and written report.
Assessment move
For the group plan, split the project into workstreams and label each clear or blurred before choosing a method. Show the traditional parts with milestones and the agile parts with sprint cadence and review points. That structure demonstrates judgment rather than enthusiasm for a single method.
Write user stories for the agile parts from your empathy-map persona, each with a short acceptance test.
Snapshots of a real backlog make the plan concrete for markers and the presentation audience.
Always include the hand-over from experimental to stable operation. Naming who owns it and which standards apply shows you understand why many promising analytics pilots never reach everyday use.
Working through Agile Methods and Bimodal IT for Analytics Projects in BUSA8030? Sia is AskSia’s AI Management tutor — ask any BUSA8030 Agile Methods and Bimodal IT for Analytics Projects question and get a clear, step-by-step explanation grounded in how BUSA8030 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
MGMT8005 Digital Innovation · MGMT8012 Managing Strategically
