I come from a mostly systems&#x2F;simulators engineering background where things were done either using waterfall or ad-hoc practices.<p>I&#x27;ve quit my job and moved for multiple reasons. What I see is that now virtually all job ads, at least web business related, require Agile.
Despite of nobody really using these at my previous company, I&#x27;m aware of TDD, CI, CD, and git workflow.<p>1) I use git workflow (_master_ is deployable, _develop_ branch for CI, _feat&#x2F;name_ and _fix&#x2F;name_ for implementations).<p>2) And I&#x27;ve done a bit of TDD so I think I have an idea of development workflow: think about the system before typing, design a test, implement until test passes.<p>3) Back where I was there were no &quot;iterations&quot;. Instead there were milestones and these were somewhere between 3-6 months. Requirements had some flexibility, but most it were set to stone.<p>4) Neither concepts of sprint. Wait. Actually there was a lot &quot;sprinting&quot; (weekends and all nighters) typically in the last weeks before the milestone deadline. Is Agile immune to this with the &quot;don&#x27;t change date only change requirements&quot; approach?<p>5) There was no daily scrum - whatever that means. I talked daily with the team when it was more convenient. And with the PM once a week or so. Daily as the milestone approached.<p>6) Pair programming whatever that is, was someone (most of the times me) sitting next to another developer when he was stuck and solve things.<p>The thing is I&#x27;ll likely have to &quot;fake it until you make it&quot; in my CV about using Agile :(<p>So am I missing any revelation here? Do I need to pick up a (snake oil?) book to fit in a new company?
Ask HN: What does Agile mean in practice at your job? (non-Agile developer here)