Avantika University Students: Shipping a Small Backend Feature in Two Weeks

Yes, you can ship a small backend feature in two weeks, provided the feature is genuinely small and you scope it before writing code. The way to do it is to split one feature into tasks of half a day or less, put a time estimate on each, and agree a definition of done up front. This guide gives you a reusable template and a fully worked authentication endpoint example.

What “small” means for a 14-day backend feature

A two-week window sounds long until you subtract setup, debugging, review and writing things down. Realistically you have about 10 working days of focused effort if you study or attend classes alongside. That is roughly 30 to 40 hours. A feature fits that budget when it meets most of these conditions:

• One user-visible outcome. “A user can log in and receive a token” is one outcome. “User accounts with roles, password reset and social login” is four.
• One data model, or two at most. Every extra table multiplies migrations, validation rules and tests.
• No new external service you have never used. Email providers, payment gateways and message queues each eat days of configuration.
• Testable from the command line or an HTTP client. If you need a front end to prove it works, the scope is too wide.
• Describable in two sentences. If you cannot, split it.

Good candidates: a login endpoint, a CRUD resource for notes or tasks, a paginated search endpoint, a file-upload endpoint with size checks, a rate-limited contact form handler.

The scoping template: one feature, broken into timed tasks

Copy this into a text file or notebook before you write any code. Fill every line. A blank line is a decision you have not made yet.

FEATURE NAME:
ONE-SENTENCE OUTCOME:
OUT OF SCOPE (at least 3 items):
INPUTS (request shape):
OUTPUTS (response shape and status codes):
DATA TOUCHED (tables / fields):
DEPENDENCIES (libraries, services):
RISKS (what could blow the estimate):
TASK LIST (each task: id, description, estimate, done-when):
DEFINITION OF DONE (checklist):
BUFFER: 20% of total estimate

Rules for estimating each task

1. No task longer than 4 hours. If it is, split it.
2. Estimate in 30-minute steps, never in “about a day”.
3. Write a “done when” phrase that someone else could check, such as “returns 401 with a JSON error body for a wrong password”.
4. Add the buffer at the end, not inside each task, so you can see where it was spent.
5. Re-estimate on day 4 and day 9. Estimates are a hypothesis, not a promise.

The definition of done for a backend feature

“Done” should be a list you tick, not a feeling. Use this as a default and trim only with a written reason.

• The endpoint returns the documented status codes for success, bad input, and unauthorised access.
• Input is validated; invalid input never reaches the database.
• Secrets (keys, passwords, connection strings) live in environment variables, not in the repository.
• At least one automated test per success path and per main failure path.
• Errors are logged without writing passwords or tokens to the log.
• A README section explains how to run the app, run the tests, and call the endpoint with an example request.
• The code is committed in small, readable commits on a branch, with the final state merged or tagged.
• A short demo (screen recording or a sequence of curl commands) proves the outcome.

Worked example: scoping a login endpoint (illustrative)

The following plan is illustrative. It is a planning example, not a record of code that was run or tests that passed. Figures are estimates for a student who already knows basic Python and one web framework such as Flask or FastAPI.

Feature header

• Feature name: Email and password login.
• Outcome: A registered user posts an email and password to /auth/login and receives a signed, time-limited token.
• Out of scope: password reset, email verification, social login, refresh tokens, admin roles.
• Inputs: JSON body with email and password.
• Outputs: 200 with {"access_token": "...", "expires_in": 3600}; 400 for malformed input; 401 for wrong credentials; 429 if the attempt limit is exceeded.
• Data touched: one users table with id, email (unique), password_hash, created_at.
• Dependencies: a password-hashing library (bcrypt or argon2) and a JWT library.
• Risks: token library confusion, timing differences between “unknown user” and “wrong password” responses, test database setup.

Task table with estimates

Spreading it over 14 days

At 28 hours, two hours a day on weekdays and a few longer weekend sessions is enough. A sensible layout:

• Days 1-2: write the scoping sheet, then T1 and T2.
• Days 3-5: T3, T4, T5. Re-estimate at the end of day 4.
• Days 6-8: T6 and T7.
• Days 9-10: T8, plus a second re-estimate. If you are behind, drop T8 and note it as a known gap.
• Days 11-12: T9 and T10.
• Days 13-14: T11, final checklist pass, demo recording, and a retrospective note.

Cutting scope when the estimate slips

Most plans slip. Decide in advance what you drop, in this order:

1. Rate limiting (document it as a known gap).
2. The protected sample route (keep token verification in a test instead).
3. Extra logging polish.

Never drop password hashing, input validation or the automated tests for the main paths. Those are the parts that make the feature credible.

Avantika University and a Two-Week Backend Feature: How It Maps to Your B.Tech

Avantika University is a state-private university established under an Act of the Madhya Pradesh legislature, at Vishwanathpuram, Lekoda, Ujjain 456006. Its B.Tech Computer Science page describes a four-year programme across eight semesters.

The Full Stack Development B.Tech page is the most useful for backend work. It lists Essentials of Data Science using Python in Semester III, Application Development Using Java and Database Management Systems in Semester IV, and Web and Desktop Application Development with Major Project-II in Semester VI. It also lists Project Design and Project Implementation, so a small backend feature built in two weeks can double as practice for those project courses. The page says its tables contain duplicated rows, and no dedicated backend course is named, so confirm the exact titles against the current curriculum.

Internships are built into the structure. On the same page, Semester IV lists an assessment-only Internship (Life and Soft Skills) of 2 credits, Semester V a Summer Internship (Technical) of 2 credits, Semester VII an Industry Internship-I or Student Exchange of 8 credits, and Semester VIII industry internship or capstone options. A short backend internship is most likely to line up with the Semester V summer slot, though only your department can say what counts. The 2023 engineering brochure also lists Internship among its course components, but it is an older document, so use the current version.

The CSE page has a placements section but gives no figures or cell details, so do not treat any listed relationship with companies as a route to a role.

Checks Before Starting a Two-Week Backend Project

• Ask your programme office which semester’s internship credit, if any, a two-week project can contribute to.
• Get the current internship guidelines, including the required duration, report and evaluation format.
• Compare the project with your Python, Java and database coursework to see what you can reuse in Project Implementation.
• Ask whether an external mentor’s letter or certificate is needed for the assessment-only internship component.
• Confirm who to contact at the placement office for approvals before you begin.

Scoping template for Avantika University students: what to check about your own context

Avantika University is described by a third-party listing, Collegedunia’s page for Avantika University, Ujjain, as located in Ujjain, Madhya Pradesh, and as approved by UGC and the Madhya Pradesh Private University Regulatory Commission. That is an aggregator excerpt rather than an official source, so treat it as a starting point and check the university’s own published information.

For this article’s topic, the practical point is that no verified rule is available here on how your university treats internships, project work, or online training: duration, credits, evaluation, required documents and whether an online internship is accepted can all differ by programme and batch. Do not assume your two-week backend project will count toward anything academic. Treat it as a portfolio item and learning exercise unless your department confirms otherwise in writing.

Your scoping sheet is useful in either case. A completed sheet, a repository and a short demo are exactly the evidence a faculty coordinator or a future interviewer can review. If you take part in the free two-week online internship at CareerSwami, which provides a free offer letter and a free completion certificate after successful completion, you can use this template as the structure of your project. CareerSwami is independent and is not affiliated with or endorsed by the university.

Verification steps for Avantika University students before you commit your 14 days

1. Find your programme’s current scheme or regulation document on the university’s official website and look for the section on internships, industrial training or project work.
2. Email your department coordinator or internship in-charge and ask: “Is a self-arranged online internship of 14 days acceptable, and does it carry any credit or evaluation?” Keep the reply.
3. Ask the training and placement or career development office whether they need an offer letter before the start date, and what format of completion certificate they accept.
4. Check your academic calendar for exams and breaks so your 14 days do not collide with an assessment week.
5. Ask whether your project report or repository must follow a specific template, and who signs off on it.

Retrospective questions to close out the 14 days

On day 14, spend 30 minutes comparing plan and reality. Add a table like this to your README or notes:

The pattern across tasks matters more than any single number. Many beginners underestimate testing and setup; knowing your own bias makes the next estimate better.

Presenting the finished feature to a reviewer

• Lead with the one-sentence outcome and a 60-90 second demo.
• Link the repository with a clear README and a short commit history.
• List what is out of scope and what you dropped, honestly.
• Show one test failing for the right reason, then passing.
• Describe one decision you made and why, such as the uniform 401 message.

Frequently Asked Questions

Is an authentication endpoint too big for a two-week backend project?

Not if you limit it to email and password login with a token. Password reset, email verification, social login and roles are each separate features and should be out of scope.

Which Python framework should I use for a 14-day feature?

Use the one you already know. Flask and FastAPI both work well for a single endpoint. Learning a new framework inside the window adds risk that your estimates do not cover.

How many hours per day do I need?

The worked example totals about 28 hours with buffer, which is around two hours on weekdays plus a few longer weekend sessions. Adjust the task list rather than the quality bar if you have less time.

What should I do if I fall behind by day 9 as a Avantika University student?

Apply your pre-agreed cut list: drop rate limiting first, then the sample protected route. Keep hashing, validation and the main-path tests, and note what was dropped in the README.

Will this project count for credit at Avantika University?

That cannot be confirmed from verified information here. Ask your department coordinator in writing whether a self-arranged online internship carries credit, and what documents they require.

Do I need a database for the login example?

Yes, a single users table is the simplest honest design. SQLite is enough for a local project, which keeps setup short.

How do I test an endpoint without a front end?

Use your framework’s test client for automated tests, and a command-line HTTP client or a REST client app for manual checks. Both let you send JSON and inspect status codes directly.

What does the CareerSwami internship give me as a Avantika University student?

It is a free two-week online internship with a free offer letter and a free completion certificate after successful completion. It does not include a stipend, academic credit or any placement promise.

Related Python & Backend Engineering guides

• Rai Technology University Students: Debugging Backend Errors Like an Intern Who Reads Logs
• Shivaji University Students: Turning a Backend Internship Into a LinkedIn Profile Update
• University of Kashmir Students: Staying Productive on Backend Internships During Connectivity Gaps
• All Python & Backend Engineering internship guides