The document discusses using agile methodology to plan lectures for teaching programming subjects. It provides an overview of agile principles like iterative development, adaptation to change, and collaborative work. The document explains key agile concepts like sprints, scrums, product backlogs and uses examples to illustrate how capacity planning and burn down charts can be applied to lecture planning. It also discusses potential challenges of the agile approach for teaching and concludes that taking frequent feedback through sprints can help iteratively improve teaching methodology.

1. http://www.iaeme.com/IJARET/index.asp 64 editor@iaeme.com
International Journal of Advanced Research in Engineering and Technology
(IJARET)
Volume 7, Issue 2, March-April 2016, pp. 64–68, Article ID: IJARET_07_02_006
Available online at
http://www.iaeme.com/IJARET/issues.asp?JType=IJARET&VType=7&IType=2
Journal Impact Factor (2016): 8.8297 (Calculated by GISI) www.jifactor.com
ISSN Print: 0976-6480 and ISSN Online: 0976-6499
© IAEME Publication
___________________________________________________________________________
OPTIMAL LECTURE PLANNING FOR
TEACHING THE SUBJECT USING AGILE
METHODOLOGY
Prof. Devendra Vashi
Institute of Technology,
Nirma University, Ahmedabad, India
ABSTRACT
In the current scenario almost all software and manufacturing companies
are following the agile approach to solve all kinds of problem. Even in the
interview student has been asked for the same. As originally they are following
Software Development Life Cycle (SDLC) or waterfall model only but in agile
way. I have tried to follow agile approach for teaching the programming
subject.
Key words: Agile, Sprint, Scrum, SDLC
Cite this Article: Prof. Devendra Vashi, Optimal Lecture Planning For
Teaching The Subject Using Agile Methodology. International Journal of
Advanced Research in Engineering and Technology, 7(2), 2016, pp. 64–68.
http://www.iaeme.com/IJARET/issues.asp?JType=IJARET&VType=7&IType=2
1. INTRODUCTION AGILE
Currently agile methodology is the latest practice in the software industry which is
used to manage all kinds of project work. Mainly software development life cycle is
the main process which follows for all the task but in different manner. Basically in
agile methodology there is a concept of scrum master who will take care of all kinds
of facilities which requires to team member and all team members has work in group,
collaboratively.

2. Optimal Lecture Planning For Teaching The Subject Using Agile Methodology
http://www.iaeme.com/IJARET/index.asp 65 editor@iaeme.com
[Figure 1 Agile Approach][1]
2. PRINCIPLES OF AGILE
1. Highest priority is early delivery and end user satisfaction
2. At any point of time agile always allow to change
3. Follow the shorter time scale to deliver the products like week or month
4. All team member has to work together
5. Motivate the team member, trust on them to get the job done nicely
6. Emphasize on one to one communication
7. Only working module is the primary goal
8. The agile methodology promotes the sustainable development
9. Emphasize on technical and design aspects
10. Simplicity
11. Team should be self-organizing
12. Always adapt changes
3. WHAT IS SCRUM & SPRINT?
Scrum is a frame work for solving the complex problem. Earlier the people were
focusing on analysis and execution at once for whole process. So most of the time
output is predictable. Now a days that can be accomplish by machine. And now day’s
requirements change quickly. And that is why frequent feedback is require and same
is to be adaptable by the system. Scrum is actually deal with the uncertainty. Scrum is
basically is taking the feedback about product and the process which is used for
getting the product.
In the scrum, Cross functional team is required. Self-organizing tem is required.
Only one sprint can be plan at a time. Only team can decide what and how much
should be delivered after execution of each sprint. Once it is decided that should not
be change during sprint. Each sprint is haven’t fix time to execute it. After each sprint
the product should be deliverable. After every sprint process and product both has to
inspect. If the product is not accepted then team may revise the process after each
sprint.

3. Prof. Devendra Vashi
http://www.iaeme.com/IJARET/index.asp 66 editor@iaeme.com
4. SCRUM ROLES
1. Product owner: product owner can be customer, product marketing manager, project
manager, program manager, or business analyst. Product owner is responsible for return
on investment. Product owner’s focus is on what than how.
2. Development team: development team may consist of document writers, user interface
designers, business analysts, testers, coders or architects. Scrum tem should be small of 3-
5 members.
3. Scrum master: scrum master can be any experienced team member or may be ex project
manager. Scrum manager does not have any management authority he is just a facilitator.
[Table 1 sprint back log with physical task board][2]
5. CAPACITY PLANNING
Sprint length is 3 weeks : 9 hours
Name of
faculty
Available days
in sprint
Available hour
per week
Total hours
available in
sprint
Total minutes
available in
sprint
DV 9 1 9 540
Buffer time (5-10%) 0.5 30
Product backlog grooming 0.5 30
Total available work time per sprint 8 480
[Table 2 Capacity Planning]
6. SPRINT BURNDOWN CHART
It is graphical representation of a planned work and buffer. It will give the predicted
scenario for the actual planning.

4. Optimal Lecture Planning For Teaching The Subject Using Agile Methodology
http://www.iaeme.com/IJARET/index.asp 67 editor@iaeme.com
[Graph 1 Sprint Burndown Chart]
7. RELEASE BURNDOWN CHART
It is a representation of a actual deleiverable task.
[Graph 2 Release Burndown Chart]
8. SOME HURTLE OF AGILE APPROACH FOR
IMPLEMENTING IN TEACHING
 frequent feedback is to be taken
 if every time new methodology will be adopted then every time faculty has to prepare
like wise
 sometime frequent experiment may not me good in teaching methodology
9. CONCLUSION
Agile methodology is the perfect approach for solving the complex problem as
frequently feedback has been taken form the product owner. And after every sprint the
process has been revised. So every time revised and customer satisfied product will be
deliverable. So by using agile methodology frequent feedback will be taken from the
students so that after every week methodology will be revised as well as new idea will
be taken to teach the topic.

5. Prof. Devendra Vashi
http://www.iaeme.com/IJARET/index.asp 68 editor@iaeme.com
REFERENCES
[1] http://agileforall.com/resources/introduction-to-agile/
[2] http://scrumreferencecard.com/scrum-reference-card/
[3] Sylvia Ilieva, Penko Ivanov, Eliza Stefanova, Analyses of an agile methodology
implementation, Proceedings of the 30th EUROMICRO Conference
(EUROMICRO’04) 1089-6503/04 IEEE
[4] A. Ahmed, S. Ahmad, Dr. N. Ehsan, E. Mirza, S. Z. Sarwar, Agile Software
Development: Impact on Productivity and Quality, 978-1-4244-6567-5/10, 2010,
IEEE
[5] Oscar Nierstrasz, Mircea Lungu, Agile Software Assessment”, 978-1-4673-1216-
5/12, 2012, IEEE
[6] Shvetha Soundararajan, James D. Arthur and Osman Balci, A Methodology for
Assessing Agile Software Development Methods, 978-0-7695-4804-3/12, 2012
IEEE DOI 10.1109/Agile.2012.24
[7] Tore Dybå and Torgeir Dingsøyr, SINTEF, What Do We Know about Agile
Software Development?, IEEE Softwar e Published by the IEEE Computer Society
0740-7459/09, 2009 IEEE
[8] Amani Mahdi Mohammed Hamed, Hisham Abushama, Popular Agile Approaches
in Software Development: Review and Analysis, 2013, ICCEEE
[9] R. Steven Wingo, Murat M. Tanik, Using an Agile Software Development
Methodology for a Complex Problem Domain, Proceedings of the IEEE
SoutheastCon 2015, April 9 - 12, 2015 - Fort Lauderdale, Florida
[10] Kaushal Pathak, Anju Saha, Review of Agile Software Development
Methodologies, Volume 3, Issue 2, February 2013 ISSN: 2277 128X, IJARCSSE
[11] Martin Kunz, Reiner R. Dumke, Niko Zenker, Software Metrics for Agile Software
Development, 1530-0803/08, 2008 IEEE DOI 10.1109/ASWEC.2008.61
[12] Malik Qasaimeh, Hossein Mehrfard, Abdelwahab Hamou-Lhadj, Comparing Agile
Software Processes Based on the Software Development Project Requirements,
978-0-7695-3514-2/08, 2008 IEEE DOI 10.1109/CIMCA.2008.54
[13] Frauke Paetsch, Dr. Armin Eberlein, Dr. Frank Maurer, Requirements Engineering
and Agile Software Development, Proceedings of the Twelfth IEEE International
Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises
(WETICE’03) 1080-1383/03, 2003 IEEE.
[14] Ms. Deepali Shahane and Dr. Pallavi Jamsandekar, A Study of Critical Success
Factors For Adaption of Agile Methodology. International Journal of Computer
Engineering and Technology, 4(4), 2013, pp. 539–546.
[15] Rahul Sindhwani and Vasdev Malhotra, Agile Manufacturing through Management
Driver. International Journal of Advanced Research in Engineering and
Technology, 6(4), 2015, pp. 34–40.